Overview
Most sales teams rely on public signals like job changes, funding rounds, and company news to time their outreach. The problem is every competitor sees those same signals. Custom API Signals let you push proprietary, first-party data into Amplemarket from any external tool, whether that's Clay, Zapier, Make, RB2B, your own product, or anything else that can send an HTTP request.
When data arrives via the webhook, Duo Copilot generates a signal and can automatically create personalized sequences for each lead. You define what constitutes a signal, a prospect filling out a form, a website visitor hitting your pricing page, a freemium user inviting teammates, an event attendee registering, and Amplemarket's AI does the rest. For high-priority signals, Duo presents recommendations for the rep to review. For lower-priority signals, Duo can run on Autopilot, executing outreach automatically.
Custom API Signals are different from Custom CRM Signals. If your data lives in Salesforce or HubSpot, use Custom CRM Signals, which pull directly from reports and lists. If your data comes from anywhere else, Custom API Signals are the way to go.
What you can do
- Send data from any external tool Push data from Clay, Zapier, Make, RB2B, Common Room, Vector, your own backend, or any tool that can make an HTTP POST request. Each signal gets a unique webhook URL.
- Track people or companies Choose whether your signal targets individual people (e.g. a specific contact who visited your site) or companies (e.g. an account showing usage growth). For company signals, Duo suggests multiple contacts from that company who match your filters.
- Trigger AI-generated outreach automatically When a signal fires, Duo picks it up, enriches the lead, and generates a personalized multichannel sequence across email, phone, and social. Reps review and approve, or Duo executes automatically in Autopilot mode.
- Add AI personalization fields Attach context fields from your data so Duo can craft relevant messaging. If the signal is "prospect visited pricing page," include fields like pages visited, form responses, or product usage data. Duo uses these to tailor the outreach.
- Write a signal prompt to guide Duo Tell Duo how to approach leads from this signal: what the signal means, how to use the context fields, and what tone or approach to take. This is how you control the quality and relevance of the outreach Duo generates.
- Detect intent moments invisible to competitors Website visitors, inbound form submissions, product usage triggers, event attendees, trial cancellations, these are proprietary signals only your data can surface.
How it works
- Set up the signal Give it a name and label (e.g. "Inbound Lead," "Website Visitor"). Choose whether it tracks people or companies.
- Configure the webhook You'll get a unique webhook URL with a token-based authentication. Copy it and configure it as the destination in your external tool (Clay, Zapier, Make, your backend, etc.). The endpoint accepts a POST request with a JSON body.
- Send test data Send a sample payload from your external tool so Amplemarket knows what data to expect. During setup, all requests are treated as test data so you can configure your mappings. No leads are generated until you save the signal.
- Review enrichment mappings Amplemarket auto-maps your fields to the identifiers it needs to match each person or company in its database. For people signals, map at least one of: LinkedIn URL, email, or person name + company. For company signals, map at least one of: company name, company domain, or company LinkedIn URL.
- Add AI personalization fields (optional) Select which fields from your data Duo should use as additional context when writing sequences. Pick fields that explain why each person is a relevant lead or what they did.
- Write your signal prompt Tell Duo what the signal is, how to use the context fields, and how to approach the leads. This guides how Duo creates recommended sequences.
- Save and go live Once saved, all subsequent requests to the webhook generate real leads. Duo checks for new leads roughly every hour and generates them up to your configured daily limit.
Use cases
Product-led growth signals
Your product analytics show that freemium users who invite three or more teammates within their first week convert to paid at a high rate. You push this event to Amplemarket via Custom API Signals from your backend. When Duo picks up the signal, it generates a personalized outreach sequence to the account's decision-maker, referencing team adoption momentum and offering an enterprise trial.
Inbound form submissions
A prospect fills out your demo request form. Your marketing automation tool sends the form data to Amplemarket via the webhook, including fields like use case, company size, and pages visited. Duo picks up the signal, enriches the contact, and generates a sequence that references their specific interest and use case. The rep sees the recommendation with full context and launches the sequence.
Re-engage lost opportunities
Your CRM tracks lost opportunities that were closed due to timing or budget. When a contact from a lost opportunity revisits your website, your website visitor tool (like RB2B) pushes the event to Amplemarket. Duo generates a re-engagement sequence that acknowledges the previous conversation and presents what has changed since they last evaluated.
Event attendee follow-up
After a conference, your event platform sends attendee data to Amplemarket via the webhook. Duo enriches each attendee, matches them against your ICP, and generates personalized follow-up sequences referencing the specific event and any session data included in the payload. In Autopilot mode, this runs without rep involvement.
Frequently asked questions
What's the difference between Custom API Signals and Custom CRM Signals?
Custom CRM Signals pull data from a Salesforce report or HubSpot list. Custom API Signals accept data from any external tool via a webhook. If your data lives in your CRM, use CRM Signals. If it comes from somewhere else (your product, a third-party tool, a marketing platform), use API Signals.
Do I need a developer to set this up?
Not necessarily. If you're using no-code tools like Zapier, Make, or Clay, you can configure the webhook without writing any code. You just need to know which fields your external tool sends.
How do I send test data?
Send a POST request to your webhook URL with a JSON body containing the fields you want to send. During setup, all requests are treated as test data for configuring your mappings. Once you save the signal, subsequent requests generate real leads.
How long until leads show up in my Duo Copilot feed?
Duo checks for new leads and generates them roughly every hour. Once your signal is set up and data is coming in, you can expect leads to appear within the next hour. Keep in mind that Duo has a daily lead limit per user, so leads are generated up to your configured limit.
What happens if Amplemarket can't match a lead with someone in its database?
By default, unmatched leads are skipped since Duo needs contact details to reach out. If your data includes an email and you want Duo to process every lead regardless of match, enable "Generate leads even if enrichment fails" in Advanced settings.






