Integration

Zapier integration

Connect outsend to your other tools with Zapier: start a business search, an email search or a pipeline, and trigger the next step when a job finishes.

Status: live. The Outsend app is listed in the Zapier app directory: zapier.com/apps/outsend.

Zapier connects outsend to the tools you already use, no code needed. A Zap can start a job in outsend, or run an action in another app when a job or a pipeline finishes.

Connect outsend to Zapier

Generate an API key on the Integrations page, in the Zapier card. You can also create one under Settings → API keys.
Copy the key right away: you won't see it again.
In Zapier, create a Zap and search for Outsend when you pick the app.
Choose a trigger or an action.
When Zapier asks you to connect your account, paste the key into the API Key field.
Zapier checks the key, then shows the email address of your outsend account.

To remove Zapier's access, revoke the key under Settings → API keys. A key generated from the Integrations page is named “Zapier”.

No account yet? Sign up here, the invite code is already filled in.

A job started from Zapier costs the same EF as a job started in the app, with the same limits (job cost).

Triggers

Trigger	Fires when
Completed Job	A job finishes and its file is ready to download.
Failed Job	A job fails.
Completed Pipeline	A pipeline finishes and its final file is ready.

Job triggers pass the job fields to the next steps of the Zap. The most useful ones: Job ID, Job Type, Results Count (number of rows), Download URL (CSV) (link to the file) and Error Message (why the job failed).

Completed Pipeline passes Pipeline ID, Pipeline Name and Pipeline Status.

Actions

Action	What it does
Create Business Search Job	Starts a job that builds a list of businesses from your search queries.
Create Email Enrichment Job	Starts an email search for the businesses in a finished job.
Create Pipeline	Creates a pipeline and starts it right away.

Create Business Search Job

Search Queries: what you are looking for, one query per line. For example plumber or real estate agency.
Zones: where to search, one zone per line. A city (Lyon), a radius (Lyon 30km), a county, a region or state, a postal code, or the whole country.
Country: the three-letter country code for the zones (FRA by default, USA, DEU…).
Optional fields: Include Reviews Data, Search Mode (fast by default, normal or ultra), Stop after ~N places, Max Rows per Phone Number and Extra Columns (gps, departement, region).

Create Email Enrichment Job

Source Job ID: the finished job whose rows you want to enrich. Map the Job ID field from the Completed Job trigger, or pick the job from the list.
The source job needs a website for each business. A business search already includes it.
Search Mode: normal (default) checks the main pages of each website. deep checks more pages to find more emails.

Create Pipeline

Pipeline Definition (JSON): the easiest way is to build the pipeline in outsend, export it, then paste the exported JSON.
The full format is documented here: GET /api/pipelines/schema.
Pipeline Name is optional.
To chain a business search and an email search, one pipeline is simpler than two Zaps: outsend runs each step on its own.

Example Zaps

Start a search from Airtable. Trigger: new record in an Airtable base with a business type and a city. Action: Create Business Search Job, with the business type in Search Queries and the city in Zones.

Tell the team when the file is ready. Trigger: Completed Job. Action: Slack message with Results Count and Download URL (CSV).

Get an alert when a job fails. Trigger: Failed Job. Action: email to the team with Error Message.

Help

Events & webhooks: the events behind the triggers.
Authentication: create and revoke an API key.
Pipeline orchestration: build a pipeline.
Questions about your integration? Reach us through the Contact page.