Webhook-Triggered Sequencer — reactive personalized outreach on demand
Webhook in, personalized email out. When an upstream system has a lead ready, it POSTs to this agent's webhook URL — the agent reads the payload, writes one tailored email, pushes to Instantly, and notifies Slack. Stateless, on demand, no cron.
The outcomes on their scorecard
Cron-based sequencers wait for the next 5-min tick. This one fires the instant the upstream system has a lead ready.
The webhook sender provides company_description + qualification_notes + everything else the email should reflect. Personalization quality is set by what you POST.
No workspace_db. The upstream system owns lead persistence. This agent is pure transform: webhook in, email out.
Optional: last char of user_id deterministically picks between two subject styles. Run subject experiments by routing user IDs.
How the work gets done
The cron-based GTM Email Sequencer pulls leads from a table on a fixed schedule. This one is the opposite: it fires reactively. An upstream system (another agent, a Stripe webhook, a Calendly hook, a custom enrichment pipeline) POSTs a lead payload with rich context — and this agent writes a single hyper-personalized email and pushes it to Instantly immediately. Stateless: no workspace_db tables, no polling. The upstream system already persisted the lead; this agent just sends. Best for high-context, lower-volume flows where every lead arrives with bespoke notes the email should reflect. Optional A/B subject variant selection by user_id last-char so you can run subject experiments without code changes.
On-demand sequencer. Fires when an upstream system POSTs a lead. Reads the payload's rich context, writes one personalized email, pushes to Instantly, notifies Slack. No DB, no cron, no state. Best for low-volume / high-context flows.
Your new teammate
Webhook-Triggered Sequencer
On-demand personalized email sender. Receives lead payloads via webhook, writes one tailored email per payload, pushes to Instantly via createLead, notifies Slack. Stateless — no workspace_db. Different motion from the cron-based GTM Email Sequencer.
What it runs on
This hire is assembled from the public toolkit. Every piece below is a tool your own agents can call too.
How setup works
- 01
Claim the hire
One click. No questionnaire. The brief is already written from your business, and you can edit it before you build if you want to.
- 02
Your hire deploys itself
Agents, tools, schedules, memory, hand-off queues and the database schema are provisioned into your workspace automatically, then the first real run fires while you watch.
- 03
Hand it the keys it still needs
You land in chat with your hire and its findings. 3 setup tasks — connecting your outreach tools, picking where it reports — are done conversationally, whenever you want.
Other hires that pair well
X (Twitter) profile qualifier and enricher
Hand any X username to this agent and get back a qualified, ICP-scored lead with a verified email and a resolved LinkedIn profile.
LinkedIn profile qualifier and enricher
Hand any LinkedIn profile URL to this agent and get back a qualified, ICP-scored lead with a verified email and a website summary attached.
Email Finder Waterfall — verified email from any combination of identifiers
Give it a name + a domain (or a LinkedIn URL, or any combo of identifiers) — it returns a verified professional email or a structured failure. Three-step waterfall: agntdata orchestrator → Exa deep search → verifier. Stateless primitive, called by other agents.
Every hire is assembled from the same toolkit.
Same data sources, same database, same memory, schedules and queues. Point your own agent at the MCP endpoint and wire it your way instead.