Connecting your tools

You can disconnect any of them from the same card. Postlude only ever stores a connection's credentials encrypted, and never shows them again.

1. On Setup (or the Fathom card on Integrations), press Connect Fathom.
2. Fathom shows its own screen asking you to let Postlude access your account. Approve it, and you come straight back to Postlude.

Postlude then asks Fathom to tell it whenever one of your recordings is ready, and drafts from it automatically. Only recordings you made are picked up, so every teammate connects their own Fathom. Disconnecting stops new recordings from arriving and removes Postlude's notification registration at Fathom.

1. Press Connect Gmail on Setup (it is the "Before you send" row) or on the Gmail card.
2. Choose the Google account you send from and approve the request on Google's screen.

Google's screen asks for two things only: to send email on your behalf and to see your email address. Postlude cannot read your inbox or your existing emails. Emails go out from your own address, and only when you press send (or approve a draft in Slack). Postlude's Google access has been through Google's own verification.

You can review or remove the permission at any time at myaccount.google.com/permissions.

1. An owner or admin presses Connect Attio on Setup or the Attio card.
2. Approve the request on Attio's screen for the workspace you want to log into.

The permissions are to read and write people, read your object settings (Attio requires this to add records and notes), and read and write notes. When you send a follow-up, Postlude finds the person in Attio by email address (creating them if they are not there yet) and adds one note listing who it went to, the subject and the email text. Postlude never reads anything back into its own contact list from Attio, and calls themselves are not logged.

There are two ways to connect, and an owner or admin does it once for the whole workspace. The one-click way is the easiest; the token way is for accounts that cannot install apps.

1. In Postlude press Connect with HighLevel (Setup or the HighLevel card).
2. On HighLevel's own screen choose one sub-account (not the whole agency) and approve. You land back in Postlude with the card showing the sub-account's name.

You can also start from HighLevel: install Postlude from the HighLevel marketplace, choose the sub-account, and the page that opens in Postlude asks you to sign in (or create an account) and press Connect HighLevel. That install link stays open for two hours; if it runs out, press Connect with HighLevel in Postlude instead.

If your account cannot install apps, use a token instead. HighLevel does not show a consent screen for this, so there are a few steps in HighLevel first.

1. In your HighLevel sub-account, open Settings and then Private Integrations, and create a new integration. Name it "Postlude".
2. Tick these three permissions: View Contacts, Edit Contacts and View Locations.
3. Copy the token. HighLevel shows it only once, so copy it straight away.
4. In Postlude press Use a token instead (Setup or the HighLevel card). Paste the token, and either the Location ID or just the address from your browser while you are inside that sub-account (Postlude finds the ID in it). The Location ID is also under Settings and Business Profile.

With the token, Postlude checks it and the location with HighLevel before saving, and shows you the location name so a wrong one is obvious. If you leave out Edit Contacts, the connection saves but the first send will mark it as needing attention, so do tick all three. Either way, when you send a follow-up, Postlude finds the contact by email (creating one marked with the source "Postlude" if it does not exist) and adds a note with the email. If you uninstall Postlude in HighLevel, HighLevel tells Postlude and the connection is removed; sent emails are then no longer logged there until you connect again.

A workspace can have either Attio or GoHighLevel connected, not both. If you want to switch, disconnect the current one first. Connecting a CRM is optional: without one, sent emails are simply not logged anywhere.

1. An owner or admin presses Connect Slack on Setup or the Slack card.
2. On Slack's own screen, choose the workspace and the channel new drafts should be posted to, then allow it. Postlude posts a short test message there to confirm it works.

• For a private channel (or a direct message), invite the Postlude app into it first with /invite, otherwise Slack will not let it post.
• Each new draft is posted with Approve. Pressing it sends the email exactly as the Send button would, from the Gmail of the person who pressed it (so they need Gmail connected), with the same checks. That person also needs the same email address in Slack as in Postlude.
• Only calls that arrive automatically are posted. A call you fix by hand afterwards is not.