Outreach
CRM OAuthManage prospects, accounts, sequences and tasks in Outreach from any Windmill script, flow or app.
Set up in 2 steps
Connect from the Resources page
Open Resources, click Add a resource/API and pick outreach under Instance-configured OAuth APIs. Click Connect, sign in and grant access, then name the resource and save it.
Run your first script
Fork any script below and read before writing anything.
Scripts
Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.
New Task
New Mailing
Update Prospect
Update Account
Pause, Resume or Finish Sequence State
List Tasks
List Sequences
List Sequence States
List Prospects
List Mailings
List Mailboxes
List Accounts
Get Sequence
Get Prospect
Get Mailing
Get Account
Create Task
Create Prospect
Create Account
Complete Task
Add Prospect to Sequence
Trigger flows from Outreach
Outreach is not only a destination. These inbound paths are supported today.
New mailings and tasks (scheduled poll)
Two trigger scripts (New Mailing, New Task) each poll Outreach and return what was created since their last run. To run one, open a flow, add a trigger and choose Scheduled Poll, then pick the trigger script and an interval. The steps after it run once per new item, and each flow keeps its own cursor.
Resource type
The shape of the credential every script on this page expects.
outreach
View raw schema →| Field | Type | Required | What it is |
|---|---|---|---|
| token | string | Yes | OAuth2 access token, filled automatically when you connect with OAuth (recommended — tokens are refreshed for you). Pasting a token minted from your own Outreach OAuth app (https://developers.outreach.io/api/oauth/) also works but it expires after 2 hours, so only do that for one-off testing. |
Questions
Can I paste a key instead?
There is none to paste. Outreach issues no long-lived API keys, so OAuth is the only path — and it is what keeps the token refreshed.
There is no Connect button on my instance
A Windmill instance admin has to add an Outreach OAuth client once, under Instance settings → Auth/OAuth/SAML → OAuth, with a client id and secret from an app in the Outreach developer portal. There is no key to paste instead.
Is my token stored on the hub?
Never. It lives only in your own Windmill workspace, encrypted at rest.