Trigger external webhooks and APIs directly from your Amplemarket sequences. Connect outreach steps to any tool with an HTTP endpoint

The HTTP Request stage is a native step type within Amplemarket sequences that lets you trigger an external webhook or API call as part of your outreach cadence. When a lead reaches this stage, Amplemarket sends an HTTP request to the endpoint you specify, passing lead data along with it.

You can place it anywhere in a sequence: at the start (to trigger personalized video generation in SendSpark), in the middle (to send a gift through Sendoso), at the end (to log data to a third-party tool), or after a branch (to route leads into another sequence). It supports POST, PUT, and PATCH methods with JSON, XML, or custom payload formats.

Instead of your sequence being limited to direct outreach actions, you can weave in automation triggers that update external systems, kick off workflows in other platforms, or log events to your analytics infrastructure. If a tool has a webhook URL or API endpoint, you can trigger it from an Amplemarket sequence.

• Trigger personalized videos Add the stage at the start of your sequence to send lead info to SendSpark. SendSpark automatically generates a personalized video you can reference in later email steps.
• Send gifts mid-sequence Place an HTTP Request stage in the middle of your sequence to trigger a Sendoso campaign. Send a small gift or coffee voucher, then follow up with an email a few days later.
• Route leads between sequences Use the HTTP Request stage to call Amplemarket's own Sequences API. Re-route leads based on what happens in the sequence, like moving them to a different sequence if they don't have an email address.
• Notify your team in Slack Fire a webhook to Slack when a lead reaches a key milestone in your sequence, keeping reps informed without monitoring the dashboard.
• Connect to any tool with an API Any platform that exposes a webhook URL or REST endpoint can receive data from your Amplemarket sequence. This includes internal tools, custom dashboards, data warehouses, and third-party platforms.
• Use dynamic lead data in payloads Include placeholders like {{first_name}}, {{email}}, and {{company_name}} in your payload. Amplemarket replaces them with real lead data at runtime.

1. Add the stage Drop an HTTP Request stage anywhere in your sequence. Configure the method (POST, PUT, or PATCH), the destination URL (must be HTTPS), headers (at least one required, typically Content-Type and Authorization), and the payload with static or dynamic fields.
2. Test before going live Run a test request from the setup screen. Amplemarket sends a dummy request with placeholder values. A 2xx response means the stage is configured correctly. Always test before saving.
3. Lead reaches the stage When a live lead hits the HTTP Request step, Amplemarket sends the request with real lead data. If the endpoint responds with 2xx, the lead moves to the next stage. If not, the lead is marked as removed by default, though you can override this in Advanced Settings to continue the sequence.

Personalized video outreach via SendSpark

Your sequence starts with an HTTP Request stage that sends each lead's name, email, company, and domain to SendSpark's API. SendSpark generates a personalized video. The next email step in your sequence includes the SendSpark snippet with the video ready to play.

Gift-triggered follow-up via Sendoso

A lead hasn't replied after three emails. An HTTP Request stage triggers a Sendoso campaign to send a coffee voucher. Two days later, the sequence sends a follow-up email: "Hope the treat brought a smile to your day. When would be a good time to connect?"

Multi-tool orchestration

Your sales process spans Amplemarket for outreach, an internal tool for proposal generation, and a separate platform for contract management. HTTP Request stages connect all three: a positive reply triggers your proposal tool, and a deal progression triggers the contract platform.