Overview
Amplemarket webhooks are outbound push notifications. When something happens in Amplemarket, your system hears about it immediately. Every time an email is sent, a reply is received, a call is made, or a meeting is booked, Amplemarket sends a JSON POST request to the endpoint you configure. Your system processes the payload and acts on it however you need.
This is different from polling the REST API. With the API, your system has to ask "did anything happen?" on a schedule. With webhooks, Amplemarket tells your system the moment an event occurs. No delay, no polling interval, no wasted requests.
It's also different from Zapier. Zapier provides a no-code middleware layer that connects Amplemarket to apps through a visual workflow builder. Webhooks skip the middleware entirely. Your endpoint receives the raw event data with no intermediary, no per-task pricing, and no dependency on a third-party platform.
What you can do
- Reply webhooks Get notified when a lead replies via email. Push reply data to your CRM, Slack, or internal tools the moment a prospect responds.
- Sequence stage webhooks Receive notifications when a lead reaches a new stage in a sequence, when an email is sent, a call is logged, or a task is scheduled.
- Workflow JSON webhooks Trigger webhooks from reply-based Workflows using "Send JSON to endpoint" actions. Route specific reply types (interested, not the right person, out of office, asked to circle back) to different systems based on the reply label. Payloads include email message data, sequence info, lead details, and additional context like referral info or follow-up dates.
- Structured JSON payloads Every webhook fires as a standard HTTP POST request with a structured JSON body. Parse with any language or framework.
- Multiple endpoint support Configure different webhook URLs for different event types. Send reply events to your CRM sync service and workflow events to your Slack notification bot.
How it works
- Registration Configure your webhook endpoint in Amplemarket's settings. Provide the URL where you want to receive events and select the event types to subscribe to.
- Event delivery When a subscribed event occurs, Amplemarket constructs a JSON payload with the event details and sends an HTTP POST request to your registered endpoint. The payload includes event type, timestamp, prospect data, sequence information, and relevant metadata.
- Processing Your endpoint receives the POST request, parses the JSON body, and executes whatever logic you need. Update a CRM record, send a Slack message, trigger an internal workflow, write to a database.
Use cases
Real-time CRM sync without polling
Your engineering team builds a lightweight service that receives Amplemarket webhooks for email sends, replies, and meetings. Each event is mapped to the corresponding contact in Salesforce and written immediately. Your CRM reflects Amplemarket activity in real time with no batch sync.
Slack notifications for high-value replies
You configure a webhook for reply events and point it at a service that checks whether the replying prospect belongs to a target account list. If they do, the service posts to your team's Slack channel with the prospect name, company, and reply context. Your AEs see high-value replies within seconds.
Route reply types to different systems
Using Workflow JSON webhooks, you route "interested" replies to your CRM for deal creation, "not the right person" replies to your enrichment pipeline (the payload includes the referred contact's details), and "out of office" replies to a scheduling queue that re-engages when the prospect returns.
Frequently asked questions
What events can Amplemarket send via webhooks?
Amplemarket webhooks can fire for email sends, replies, calls, and meetings booked. Workflow JSON webhooks provide additional context based on reply labels, including referral info for "not the right person" replies, return dates for out-of-office replies, and follow-up dates for "asked to circle back" replies.
How are webhooks different from the Amplemarket REST API?
The REST API is pull-based. Your system sends requests to retrieve data on a schedule. Webhooks are push-based. Amplemarket sends data to your system the moment an event occurs. Use the API for querying historical data or performing actions. Use webhooks for reacting to events in real time.
How are webhooks different from using Zapier?
Zapier is a no-code middleware that connects Amplemarket to other apps through a visual interface. Webhooks send raw JSON directly to your endpoint with no intermediary. Webhooks are better for engineering teams that want full control, lower latency, and no per-task costs. Zapier is better for non-technical users who need quick integrations without writing code.
What data is included in a webhook payload?
Webhook payloads include the email message details (from, to, subject, body, snippet), sequence information (name, stage, start date), user data, and lead details (email, name, company, domain). Reply-based webhooks also include the reply label and any additional context relevant to that label type.
Can I send webhook data to Slack without Zapier?
Yes. Configure a webhook endpoint that points to a small service or a Slack incoming webhook URL through a lightweight function. When Amplemarket fires a reply event, your service formats the data and posts it to Slack directly. No Zapier account needed.







