Our primary native transcript integration. OAuth connects your Fireflies workspace — transcripts flow in automatically after every call.
- One-click OAuth
- Auto-ingest, no webhooks
- Works on every plan
- Full meeting metadata
Scurry doesn't replace anything. It connects — to your meeting tool, your inbox, your CRM — and handles the follow-up sequence in between.
Native OAuth • Free forever • No credit card
Every tool Scurry touches slots into one of three places — transcript in, email out, CRM on the side.
Whatever records and transcribes your calls. Fireflies is native OAuth; everything else POSTs to our open endpoint.
Emails go out through your own mailbox — your name, your domain, your reputation. One inbox is enough.
Reply detection runs in real time on both — sequences auto-stop the moment a prospect writes back.
Wire in your CRM for deal-stage checks, conditional sending, and push-back writes. Completely optional.
Don't use a CRM? Skip this column. The core product works without one.
No webhooks to configure. No passwords stored. OAuth hands Scurry a scoped token and the pipeline is live.
Our primary native transcript integration. OAuth connects your Fireflies workspace — transcripts flow in automatically after every call.
Deep native CRM integration. Deal-stage checks, smart filtering, and send-time conditional logic — so stale sequences never hit closed deals.
Emails send through your own Gmail — your name, your address, your domain. Scurry never sees your password. Pub/Sub powers real-time reply detection.
Full Microsoft 365 support via OAuth. Graph subscriptions handle real-time reply detection on the Outlook side — same zero-password model as Gmail.
*Required means you need one inbox connected to send — either Gmail or Outlook. Pipedrive is optional.
If your tool produces a transcript and can send HTTP, it works with Scurry. Point a webhook at our endpoint — same sequence, same pipeline, no native integration required.
# POST a transcript, get a sequence POST https://api.scurry.ai/v1/transcript Authorization: Bearer sk_your_key Content-Type: application/json { "meeting_title": "Discovery · Acme Corp", "transcript": "...", "workflow": "inbound_discovery", "participants": 3 }
One HTTP call. Scurry handles the rest. Full endpoint reference →
These are meeting platforms, not transcript tools — they don't push transcripts to outside apps. But the fix doesn't change how you run meetings at all.
Different teams find Scurry different ways. Jump straight to the page that matches your use case.
One-click OAuth for the four tools most teams already use. Open endpoint for everything else.
Free forever · Native OAuth on all plans · No credit card required