Webhooks, the API and the MCP server
Send Hollerly events to your systems with signed webhooks, use the REST API with an API key, connect Zapier or Make, and use the MCP server with AI tools.
Webhooks (Pro and up)
Under Settings, Integrations, add an Endpoint URL (https) and pick events:
- lead.replied and meeting.booked (ticked by default)
- lead.tagged, lead.accepted, lead.stage_changed, lead.unsubscribed and message.sent
Hollerly sends a JSON POST with the event, the time, your workspace, the lead and event data. Each webhook has its own secret (Reveal, Copy). Every request carries an X-Hollerly-Signature header with an HMAC SHA-256 of the raw body, so you can check it came from Hollerly. Use Send test to try it. If your endpoint answers HTTP 410, the webhook turns itself off. You can have up to 100 webhooks.
The endpoint URL must start with https:// and use the standard port (443), and its host must be a public internet address, not a private or local network. Otherwise you'll see a message such as "That address isn't reachable from the internet". Redirects aren't followed, so use the final URL. The same rules apply to REST hooks created through the API.
API keys (Agency)
Under API keys, enter a Key name and click Create key. Copy it straight away, because it won't be shown again. Send it as a bearer token in the Authorization header. You can have 20 active keys and revoke any of them.
The API lets you list campaigns, add up to 500 leads to a campaign, read leads and replies, update a lead's stage, tags and deal value, and pause or resume campaigns. Full reference: API docs.
Zapier and Make
There's no listed Zapier or Make app. Connect them with an API key: create a REST hook through the API to get events, and call the API to add leads. In Make you can also use the HTTP module. The API docs have the details.
MCP server (every plan)
Hollerly runs an MCP server at https://hollerlyai.com/api/mcp. AI assistants that support MCP can then list campaigns, read stats and replies, add leads, change a lead's stage, and pause or resume campaigns. Only the workspace owner or an admin can connect one.
Connect Claude in one click
- In Claude (claude.ai or the desktop app), open Settings, Connectors and click Add custom connector.
- Name it Hollerly and paste https://hollerlyai.com/api/mcp as the URL. Leave the advanced OAuth fields empty.
- Click Add, then Connect.
- Sign in to Hollerly if asked, pick the workspace and click Allow.
Connect ChatGPT in one click
- In ChatGPT, open Settings, Connectors and add a custom connector. You may need to turn on developer mode under Advanced first.
- Name it Hollerly, paste https://hollerlyai.com/api/mcp as the URL and choose OAuth for authentication.
- Click Connect, sign in to Hollerly, pick the workspace and click Allow.
Connected apps are listed under Settings, Integrations, Connected AI apps. Click Disconnect to cut an app off straight away. To point an app at a different workspace, disconnect it and connect again.
Developer tools (API key, Agency)
Claude Code, Cursor and other tools that take a header can use an API key instead (API keys are on the Agency plan): send it as Authorization: Bearer with the same URL. The API docs show the exact command and config.
Usage limits
Each MCP connection, whether an app you connected or an API key, can make up to 600 requests an hour, and a batch can hold up to 20 requests (each one counts toward the hourly limit). Over the limit, the app gets the error "Rate limit: 600 requests an hour per connection". The count resets at the start of each hour (UTC). AI writing you start in the Hollerly dashboard, such as drafting samples or reply drafts, has its own daily allowance per person: 300 by default, reset at midnight UTC.