Close · Connectors
A card that says connected means a credential that worked
Twelve third-party accounts across booking, CRM and automation. Every one of them is a live call rather than a stored string: saving verifies against the vendor's own API before the row is marked connected, and the vendor's answer supplies the label on the card.

HubSpot
Connected

Slack
Connected

Google Calendar
Connected

Attio
Connected

Zapier
Not connected
Webhooks
Connected

Pipedrive
Not connected

Cal.com
Not connected
What is actually going on
Every claim below is followed by the mechanism under it, because a claim without a mechanism is a slide.
Every reply, opt-out and booked meeting fans out
A contact record and a note reach the CRM. The same events reach a Slack channel, a Zap, or your own signed endpoint.
A missing signing secret is a refusal, not a warning
Webhook deliveries carry an HMAC signature over the timestamp and body. The secret is generated on save, shown once, and stored outside the config any connector-viewer can read.
Delivery is queued and retried
Five-minute backoff doubling to six hours, dead after eight attempts, twenty-five per pass as tail work on the reply poller's tick.
The agency case is a first-class field
Go High Level's location field is required rather than decorative, because one location per client is the whole reason an agency attaches it.
Step by step
How crm & alerts runs
- 1
Attach
Paste the credential. It is called against the vendor before it is stored.
- 2
Map
Contacts, notes and the events you want out.
- 3
Fire
Replies, opt-outs and booked meetings dispatch on the poller's tick.
- 4
Recover
A failure queues rather than degrading, and surfaces the vendor's own reason on the card.
The numbers
Facts, not adjectives
Every figure here is a real value from the running product. A cadence from the scheduler, a price from the credit table, a limit from the ramp. A marketing page that invents a limit is a support ticket with a delay on it.
- CRMs
- HubSpot, Pipedrive, Attio, Salesforce, Zoho, Go High Level
- Booking
- Google Calendar, Calendly, Cal.com
- Alerts
- Slack, Zapier, signed webhook
- Signature
- X-TryGTM-Signature, HMAC-SHA256
- Failure mode
- Queued and retried, card shows the vendor's reason
CRM & alerts, honestly
Can I send through my sequencer?
No. Nothing sends through a third-party sequencer, which is why that whole integration category was removed rather than left unbuilt.
What happens if a CRM is unreachable during a reply?
The reply still lands, the sequence still stops, and the CRM event queues. The poller is not allowed to fail on a connector.
Close
Every reply, in one place, worked to a call
CRM & alerts is one part of it. The rest runs too.
Sourcing, enrichment, intent, copy, sending, replies and reporting are one product with one bill and one gate. Connect a channel and the whole motion starts.
Start with sales. $2,000 or $5,000 onboarding, then at least $250 monthly credit funding.