Integrations
Hearth stands on its own, and it connects to the systems around it when you want it to. Every connection below is off until you turn it on, and each one that writes to another system starts with a dry run that reads both sides and writes neither.
Most of these are run by hearthctl, the command line that ships in the same image as Hearth, and by scheduled jobs the Helm chart can create. Run hearthctl as a one-off job on the live image with the same settings as the Hearth deployment, dry run first.
| Connects to | What it does | How it runs |
|---|---|---|
| EmberOps | Accounting records for your customers and suppliers, or the whole back end | Chart settings and hearthctl crm-sync |
| Mautic | Email marketing, with every contact, segment, and unsubscribe kept in step | hearthctl mautic-sync, every ten minutes |
| HubSpot | Brings in what changed in HubSpot since the last import | hearthctl hubspot-import |
| Google Workspace groups | Group members follow Hearth teams and departments | hearthctl groups-sync |
| Your Google account | Your calendar and mail, as you | Settings, then Password and sign-in |
| Sign-in provider | Single sign-on and directory provisioning | Chart settings |
| An assistant | Search, read, and update Hearth as you | A connector at /mcp |
EmberOps
EmberOps runs your accounting and operations. Hearth connects to it in two ways.
CRM sync
Hearth owns companies, contacts, types, tags, deals, and the timeline. EmberOps gets a copy of what accounting needs, so an invoice can be raised against a real customer or supplier.
- A company whose type has a customer role becomes a Customer in EmberOps, and one with a supplier role becomes a Supplier. A company with no role, such as a prospect, does not go unless you turn on prospects, which sends it as a Lead with its people as Contacts.
- Hearth sends only the fields it owns. Credit limits, payment terms, accounts, and anything else only accounting knows are never sent and never read back.
- Every EmberOps record carries a link back to its Hearth page, and a company, contact, or deal in Hearth shows an In EmberOps link to its record.
- A customer or supplier made in EmberOps with no Hearth record behind it comes back as a Client or Vendor type on the matching Hearth company, or as a new company.
- A record that has not changed since the last run is not sent again, so a large CRM costs a handful of writes an hour.
- Optionally Hearth also sends deals as Opportunities, and sends each note and call as a comment on the matching EmberOps record, one way.
Turn it on in the chart with crmSync.enabled, after reading a dry run: hearthctl crm-sync reads and prints, and hearthctl crm-sync -write writes. -only limits a run to named companies.
EmberOps as the back end
Hearth can also run as a front end for EmberOps. Tasks, work orders, assets, documents, time, time off, the calendar, rules, saved views, parts, maintenance plans, and downtime then live in EmberOps, and staff see the same records from either app. What EmberOps does not hold, such as channels, mail, sessions, and the audit log, stays in Hearth's own Postgres.
This needs single sign-on, because each call to EmberOps is made as the signed-in person and EmberOps's own permissions decide what they may do. Turn it on in the chart with emberops.enabled, and move the records across first with hearthctl emberops-migrate. Never switch it on by itself, because the records have to be there first.
Mautic
Hearth is the CRM, and Mautic sends the email and records what people do with it. hearthctl mautic-sync keeps them in step in both directions, and the chart runs it every ten minutes when mauticSync.enabled is on.
Out, from Hearth to Mautic. Every contact with a usable email address becomes a Mautic contact, matched on that address so one someone already put in Mautic is adopted and not doubled. Its company becomes a Mautic company, and the owner carries across when their email matches a Mautic user. Hearth keeps segments for you: all contacts, one per company type, and one per free tag. Take a type away in Hearth and the contact leaves that segment. A contact that is deleted or loses its address leaves every segment and is tagged so no campaign reaches it. Nothing is ever deleted in Mautic.
Back, from Mautic to Hearth. Each of these becomes one note on the contact's timeline, and on its company's, written by Mautic: email sent, opened, a link clicked, a form submitted, unsubscribed, bounced, or marked do not contact. Each is keyed on the Mautic row it came from, so a repeated or interrupted run adds nothing twice.
Opt-outs. A contact Mautic marks do not contact for email, whether by an unsubscribe, a bounce, or a person, is opted out in Hearth, and the contact page says so. A contact opted out in Hearth gets the do-not-contact in Mautic on the next run. Nothing clears an opt-out. The sync does not, the API does not, and the contact page does not.
What it does not do. It does not send email, because campaigns are built and sent in Mautic. It does not create Hearth contacts from Mautic contacts or form submissions.
It needs the address of your Mautic and an OAuth2 client for it, kept in a Secret the chart names in mauticSync.secretName.
HubSpot
If your sales work is still in HubSpot, hearthctl hubspot-import brings in what was created or changed there since the last import: companies, contacts, deals, notes, and calls. It reads HubSpot with a private app token and writes only through Hearth's CRM, so every record gets its grants, its audit row, and a share with the Sales team.
- Each kind of record keeps its own mark, the newest change an applied run read, so the next run asks HubSpot only for what changed.
- A HubSpot record is matched to Hearth by its HubSpot id, then a company by web address and a contact by email address. A match is linked and brought up to date, and nothing is created twice.
- A blank in HubSpot never clears a value, and a field somebody edited in Hearth is never overwritten. It is listed in the report as a conflict.
- Nothing is deleted.
- Unsubscribes and bounces in HubSpot become Hearth opt-outs, which the Mautic and EmberOps syncs then carry on.
Run it without -apply first. The dry run reports, by object and field, how many values fill a blank and how many replace one, so a run about to touch thousands of records shows what kind of change it is before you say go.
Google Workspace groups
hearthctl groups-sync makes the members of Google Workspace groups follow the teams and departments people belong to in Hearth. You write a mapping file that names each group and the teams and departments whose people belong in it.
{
"mappings": [
{"group": "crew@example.com", "teams": ["Crew"], "departments": ["Operations"]}
],
"protect": ["admin@example.com"],
"remove": false
}
The rules it keeps:
- Removals are off unless you set
"remove": true. Off, it only adds, and the report marks each extra memberkeep, so nobody loses access until you choose that. - A mapping that names a team or department Hearth does not have is refused, because it would read as an empty group.
- Only plain members are added or removed. Owners and managers are never removed, and an address on
protectis never removed from any group. - A suspended account is not wanted, so it comes off the group.
- A dry run is the default. Add
-applyto make it so.
Where your Google organization forbids service account keys, it runs keyless: Hearth gets a token from Vord and trades it with Google for a short-lived credential. Elsewhere it can use a service account key file. The chart's groupsSync settings create a scheduled job for it.
Your Google account
Each person can connect their own Google account from Settings, then Password and sign-in, when the administrator has turned the connection on. Hearth then reads their calendar into Hearth, can put Hearth events in their Google calendar, and can read or send mail as them, only as far as they allow. See Sign in and account.
Sign-in provider
Single sign-on works with Vord and with any OpenID Connect provider, and a directory that speaks SCIM can provision people and teams. Set it up in Install Hearth, and see Administer Hearth for provisioning.
An assistant
Hearth has an assistant connector, so an assistant can search, read, and update Hearth as you, with exactly your permissions. See Connect an assistant.
Webhooks and the API
For anything else, Hearth has a REST API with bearer tokens and signed webhooks. See Administer Hearth.