Outbound Integrations with Drip

This guide is intended for developers that would like to send subscribers and events from Drip into their application, on behalf of their users.

If you’re a CRM, your integration might create a new lead in your application when a subscriber hits a certain lead score in Drip.

If you’re an SMS provider, your integration might send an SMS message when a subscriber reaches a certain point in a Drip Workflow.

If you would like to send subscribers and events into Drip, refer to our inbound integration guide.

Before You Start

Before you start your integration, contact us so we can work out the specifics of your implementation.

Authentication

The best user experience uses OAuth – this turns authentication into a 1 or 2-click process. If you offer OAuth for your application please let us know when you contact us.

The other option if you don’t offer OAuth is for your user to copy an API key from within your application and paste it into Drip. If your integration will use this approach please let us know when you contact us. We can include this as a step in our integration instructions.

Receiving data from Drip

Drip will send subscriber data in JSON format, as shown below:

If you need to add existing parameters to the payload, submit them to us when your integration is ready to go live, using this form.

Testing Your Integration

Once your endpoint is ready to accept incoming calls, you can test your integration in Drip using our “HTTP Post” automation action.

Going Live

Once your integration is tested and live, provide your URL endpoint(s), data format, action names, and OAuth or API Key instructions here and we will evaluate adding your application to our list of native actions inside Drip:

Get In Touch

We love to hear about new integrations. If you have questions along the way, don’t hesitate contact us!