Integrations
Twelve accounts, and every one is a live call
Saving a connector calls the vendor before the row is marked connected, so a card reading Connected means a credential that worked once against the real endpoint rather than a string somebody pasted correctly.
HubSpot
Connected
Slack
Connected
Google Calendar
Connected
Attio
Connected
Zapier
Not connected
Webhooks
Connected
Pipedrive
Not connected
Cal.com
Not connected
Booking
The calendar an agent books against, and the moment it tells everything else.
Google Calendar
Direct availability and booking
Calendly
Your existing event types and rules
Cal.com
Self-hosted or cloud
CRM
Receives a contact record and a note on every reply, opt-out and booked meeting. Delivery is queued and retried rather than dropped.
HubSpot
Contacts, notes, lifecycle
Salesforce
Leads, contacts, tasks
Pipedrive
Persons, notes, activities
Attio
Records and entries
Zoho CRM
Contacts and notes
Go High Level
One location per client, required rather than decorative
Automation and alerts
The same events, out to a channel, a Zap, or your own signed endpoint.
Slack
A message the moment something happens
Zapier
Everything downstream of that
Webhooks
Signed, your endpoint, your schema
What fires
Three events, and none of them is a poll
A reply, an opt-out and a booked meeting each dispatch on the poller’s own tick, carrying the contact record and a note. There is no separate sync job and nothing for you to schedule.
- Dispatch cadence
- On the reply poller's tick
- Retry policy
- 5 min doubling, cap 6 h
- Dead after
- 8 attempts
- Budget per pass
- 25 deliveries
- Webhook signature
- HMAC-SHA256 over timestamp.body
- On failure
- Queued, with the vendor's reason on the card
Beyond the grid
Or drive the whole workspace from your own assistant
One MCP endpoint, and the install snippet is a bare URL because everything else is negotiated. Fifteen tools covering workspace state, contacts, conversations, agents, signals, integrations and the prospect database, and none of them can send a message to a prospect.
Your scopes, not the workspace's
A viewer who connects an assistant gets an assistant that can read. Membership is re-read on every call.
Discovery is the protocol's job
The client finds the authorization server from a 401, registers itself, and authorises with PKCE.
Nothing sends
Outbound carries a verdict and a platform-injected footer produced by the launcher. An assistant able to send would be a way around it.
Integration questions
What does connected actually mean on a card?
That the credential you pasted was called against the vendor's own API and worked. Saving verifies before it stores, refuses on failure and leaves the previous row untouched, and the label on the card comes from the vendor's answer rather than from what you typed.
What happens when a CRM is unreachable?
The event is queued and retried with backoff: five minutes doubling to six hours, dead after eight attempts, twenty-five per pass as tail work on the reply poller's tick. The card shows the vendor's own reason. What does not happen is the reply poller failing. That poller is also the path that stops sequences for people who already answered.
Can I send through my sequencer?
No, and the whole outreach-tool integration category was removed rather than left unbuilt. Nothing sends through a third-party sequencer, because sending is your own domains and your own LinkedIn account behind our gate.
How are webhooks secured?
An X-TryGTM-Signature header carrying an HMAC-SHA256 over the timestamp and the body. The secret is generated on save, shown once, and stored outside the config that any member with connector view access can read. A missing signing secret is a refusal rather than an unsigned delivery.
What about enrichment tools?
Data and enrichment left the integrations grid because they are platform-managed: configured for every workspace from our side, so a card inviting you to attach one would describe a capability you could neither switch on nor off.
Something is missing. Can you add it?
Ask. The adapters are one client per provider behind a verify-and-deliver interface, so a new CRM is a day rather than a quarter, and the ones that get built are the ones customers name. Write to support@trygtm.com.
Need one that is not here? Tell us which and what event you need out of it. support@trygtm.com.
Keep reading
All featuresEverything above, running on your list
Describe the company, confirm the keywords, connect a channel. The agents take it from there, and Supervised mode is available when you want to review before sending.
Start with sales. $2,000 or $5,000 onboarding, then at least $250 monthly credit funding.