Works with the tools you already use

The AI Setter sends your Calendly link when the lead is ready to talk. Each booking made through it is matched to its conversation.

• The link goes out in the DM at the right moment, in your voice.
• A booking marks the lead as booked, with the meeting time.
• The booking reaches your other tools as a webhook event.

Needs: A plan with the AI Setter. Bookings report back on Calendly plans with webhooks (Standard and up).

The AI Setter agrees a time with the prospect in the DM and books the call straight into your calendar.

• Reads only when you are busy, never what your events say.
• Offers free times under your rules: working hours, length, buffer, notice, meetings per day.
• Asks for an email, creates the event with a Google Meet link, then confirms in the DM.

Needs: A plan with the AI Setter.

Leads you message become HubSpot contacts, and HubSpot workflows can enrol, pause or stop DMs.

• Contacts with DM Hero properties, stage and notes.
• A task when a lead needs you, a deal and a meeting for each booking.
• Workflow actions to enrol, pause or stop DMs (HubSpot Professional and Enterprise).

GoHighLevel

CRM·Direction: DM Hero pushes contacts into it

Every lead DM Hero works on Instagram becomes a GoHighLevel contact, kept in step as the lead moves.

• Contacts with tags, fields and notes from the conversation.
• An optional opportunity that follows the lead's stage.
• A GHL workflow can add a contact to a DM Hero campaign through the API.

Short notifications in two private channels, each with a button to the conversation and no conversation content.

• Conversations: replies to cold DMs, handoffs from the AI Setter, messages nobody will answer automatically.
• Important updates: booked and canceled meetings, and anything that blocks an account.
• You pick which kinds you receive.

Connect DM Hero to the thousands of apps on Zapier with webhooks and the REST API.

• Catch DM Hero's signed webhooks in a Zap: a reply, a booked call, an opt-out, a handoff to you.
• Send leads from a Zap into a DM Hero campaign through the REST API.
• Every event carries the lead, the campaign and a link back to the conversation.

Build Make scenarios on DM Hero events, and feed leads back into your campaigns.

• Catch DM Hero's signed webhooks in a scenario: a reply, a booked call, an opt-out, a handoff to you.
• Send leads from a scenario into a DM Hero campaign through the REST API.
• Every event carries the lead, the campaign and a link back to the conversation.

Run DM Hero events through your n8n workflows, cloud or self-hosted.

• Catch DM Hero's signed webhooks in a workflow: a reply, a booked call, an opt-out, a handoff to you.
• Send leads from a workflow into a DM Hero campaign through the REST API.
• Every event carries the lead, the campaign and a link back to the conversation.

Clay

Enrichment·Direction: Leads in, results out

Push leads from a Clay table into DM Hero and enrol them in a campaign, then get the results back as rows.

• Enriched leads go straight into a campaign.
• Replies, bookings and opt-outs come back to the table.
• A ready API key preset with exactly the permissions Clay needs.

Leads, campaigns, conversations and analytics from your own systems, with versioned, documented endpoints.

• Create leads and enrol them in campaigns.
• Read conversations, stages and analytics.
• Signed webhooks for every event you subscribe to.

Let your AI agents work with DM Hero through the Model Context Protocol, with the same API key and permissions.

• Agents can look up leads, campaigns and conversations.
• They act only within the permissions of the key you give them.
• No separate setup: the same key works for the API and MCP.