Sync sequencer replies to Attio stages and tasks
A Kestrel build, not client work, tested in our own Attio workspace. A reply event comes in, Jev classifies the reply, the person's entry on the outbound list moves to the matching stage, the reply is saved as a note, and a warm reply gets one follow-up task. The test used five simulated replies with example.com addresses, written in the shape a sequencer webhook sends. No real replies and no real sequencer were involved.
Works ifYou run sequences in one or more tools and want every reply to update Attio without copying it over by hand.
Built asDeepline PlayWebhook per replycapped at $0.10 a run
Get the prompt for your coding agentThe system
Sequencer reply webhook
Event ID, email, text, time.
LinkedIn reply webhook
Needs the LinkedIn lookup first.
Jev
What kind of reply is this?
List entry
Stage, sentiment, event ID
Note
The reply text
Task
Warm replies only
Due in 24 hours.
What it solves
A prospect replied to a sequence, by email or on LinkedIn.
Why it matters
Replies are the one signal every outbound play ends in. When they stay in the sequencer, the CRM stage is wrong, warm replies wait, and reporting on what worked is guesswork.
How it works
Take one reply event
The event is validated against one shape: event ID, sequencer, channel, email, reply text and time. The person is found or created in Attio on the email address.
Gate: seen this event before?
The person's entry on the outbound list is read first. If its last event ID matches, the event is a replay and nothing else happens.
Classify with Jev
One choice question: positive, neutral, negative or out of office. A referral to a colleague or a question counts as neutral.
Write back to Attio
The list entry gets the stage, sentiment, sequencer, channel, reply time and event ID. The reply text goes on the person as a note, with the sentiment and confidence in the title. Positive and neutral replies get one task, due 24 hours after the reply.
Build notes
- The list entry is updated before the note and the task, so a retry after a crash is still recognised as a replay.
- Only the last event ID per person is stored. A replay of an older event that arrives after a newer one would be processed again.
- It matches people on email. HeyReach and other LinkedIn tools send a LinkedIn URL, not an email, so for those the LinkedIn lookup from the post engagers build has to come first. The test gave the LinkedIn reply an email address.
- An out-of-office reply doesn't move the stage. It is saved as a note, so the sequence can carry on.
Questions
Which sequencers does it work with?
Any tool that can send a reply webhook. The play takes one event shape (event ID, sequencer, channel, email, reply text, time), so the only tool-specific part is mapping your sequencer's webhook to it. The test events used the Instantly, lemlist, Salesforge and HeyReach names, but no sequencer was connected.
What happens when a sequencer sends the same webhook twice?
Nothing. The event ID is stored on the person's outbound list entry, and an event with the same ID is skipped before anything is classified or written. In the test the first event was sent a second time and was skipped.
More builds
All builds →Find contacts at companies with 2 to 10 staff
Your buyers work at companies too small for contact databases to cover.
Build lead lists with checks before shipping
Your lead lists go straight into email campaigns and cold calls, and one wrong name costs you trust.
Enrich Attio companies and write a fixed fit score
You want every company in Attio scored the same way, with the reason written next to the score.
The next step