Sequences that know your meeting and your pipeline.
Connect Pipedrive once and Scurry reads the deal before it sends: stage, owner, open activities, so a sequence holds when the deal has already moved. Pipedrive is optional. Without it, sequences are still written from the transcript.
Three ways CRM data makes sequences smarter.
Read the pipeline when it matters. Pipedrive data powers your follow-up checks, while the Redwood-and-up Action component handles explicit writes when you configure them.
Deal-stage awareness, checked at send time
Scurry re-reads deal status right before every email goes out. If a deal closed, changed owner, or moved stages since the sequence queued, it adapts, or kills the send entirely.
Smart filtering on any CRM field
Write rules that read Pipedrive data as conditions. Deal value, custom fields, owner, updated timestamp, anything in your CRM can gate a send.
Contact + company context, automatic
Scurry fills emails with real Pipedrive data: contact, company, deal value, custom fields. Your follow-up reads like it was written by the rep who closed the call.
One deal. One filter check. One send decision.
Before an email leaves your queue, Scurry pulls fresh Pipedrive data, runs your rules, and applies the send-time check.
pipedrive
/
deal/8421
scurry
/
queue/acme-corp
If stage changed to Won or Lost between queue time and send time, Scurry would pause the rest of the sequence automatically. See all AI filter conditions →
Three clicks. Then it just runs.
Connect once from the Pipedrive Marketplace or Scurry settings. Everything else is automatic after that.
Install
Install from the Pipedrive Marketplace, or connect from Scurry settings. One OAuth click, no keys to copy.
Configure
Pick which fields your filters should read. Map Pipedrive stages to sequence actions. Everyone gets the same rules.
Done
Every new sequence inherits your rules automatically. Every send checks Pipedrive first. No maintenance.
What Scurry reads, and what it doesn't.
Read-only by default. Your Pipedrive stays clean. Intelligence flows in; noise doesn't flow out.
✓Scurry reads from Pipedrive
🚫Scurry does not write back
Want writes? The Action component is available on Redwood and Ancient Forest and can push data to Pipedrive via configured endpoints: create activities with field mapping, fire events, etc. It's opt-in and user-configured. Oak's core integration stays clean and read/check oriented.
Install from the Pipedrive Marketplace in one click.
Scurry is a verified Pipedrive Marketplace app. Install there for the fastest setup, or connect through Scurry's integration settings: either way, same OAuth, same scope, same result.
How Pipedrive users actually use Scurry.
The rep who never forgets
20+ discovery calls a week. Every call ends with "I'll send you something." Before Scurry: 60% of follow-ups were generic templates sent hours late. Now: every transcript generates a sequence written from the call automatically, gated by Pipedrive stage.
Closing deals while running the company
Running everything and closing pipeline. Follow-ups slip because something urgent always lands. Scurry handles the sequences; Pipedrive stops sends to any deal that's already won, lost, or past due.
Consistency across 10 reps
Ten reps, ten follow-up styles. Universal Prompts lock brand voice. AI Filters enforce quality. Pipedrive checks prevent embarrassment. Set the rules once, every rep's output stays on-brand and on-policy.
Pipedrive integration questions.
Already use Pipedrive? Sequences get smart the moment you connect.
One OAuth click. Every follow-up from that moment on reads your pipeline before it sends.
Included on every plan · No card to join the waitlist