Connected to where the work already happens
Four working integrations, each of which creates real CRM records rather than just showing you a feed.
Send from your own address, keep the thread
Connect your own Gmail, or one shared mailbox for the whole account. Mail you send goes out through Gmail as normal, so it lands in your Sent folder and looks like you sent it — because you did.
- Replies sync back automatically every few minutes
- Threads attach to the contact as a conversation, and appear in a shared inbox
- Quoted reply text is stripped, so the thread stays readable
- Sent and received mail is written into the contact's activity timeline
- An inbound reply notifies whoever sent the last message
Access tokens are encrypted at rest. Disconnecting deactivates the connection rather than deleting your mail history.
A booking becomes a deal, not a calendar entry
Connect your Calendly organisation and choose which event types should reach the CRM. Everything else is ignored, so an internal one-to-one does not create a sales record.
- The invitee is matched by email, or created as a new contact
- Their latest open deal is reused, or a new one is opened
- A confirmed appointment is created with the meeting link
- Both are assigned to the teammate who hosted the booking
- A cancellation in Calendly cancels the appointment here
Incoming callbacks must come from Calendly's published address range and carry a valid signature.
REST API
Push contacts, deals and appointments in from a landing page, an automation tool or your own product. Issue a bearer token from settings, revoke it whenever you like.
Nested contact details are matched or created for you, and an email-domain blocklist keeps obvious junk out.
Cloudflare Turnstile
Add your Turnstile keys and every public capture form is protected against automated submissions, verified on the server rather than in the browser. Keys are stored encrypted, and configured per account.
MCP Preview
Groundwork for connecting AI assistants to your CRM through the Model Context Protocol. The authorization layer is built — a client can discover the server, ask for your consent, and hold a scoped token.
Not yet usable: the endpoint those tokens will open is still in development. We would rather say so than list it as shipped.
Something else you need connected?
The REST API covers most one-way integrations today. Tell us what you are trying to join up and we will tell you honestly whether it is possible now, soon, or not on the cards.
Get in touch