Start sending data with IFTTT

If you don’t have an IFTTT account, start by creating one over at IFTTT.com.

IFTTT is a great option for connecting to devices, web apps, or services for things like:

• Turn on a light in your office when you get a new “plan_enterprise” user
• Create a calendar event to follow up users who enter the “Signed Up” segment
• Email to your success team when a user triggers “payment_failed”

Create your recipe

In your IFTTT account, create a new recipe. Select the “Maker” channel and select “Receive a web request”.

Give your event a descriptive title, like user_upgraded_plan.

Choose a service to connect to

Pick which of the 300+ services should be activated by this event.

Format your data and create your action

If your recipe allows you to pass along data, take this opportunity to configure it.

Once you’re done, you can create your action and your recipe.

Create your campaign in Customer.io

If you’re starting a new campaign, you can create one now.

Inside your Customer.io account, create your campaign— it can be event triggered or segment triggered.

Add and name your webhook

In Customer.io, add a new webhook action in the campaign’s workflow and give it a name.

You then need to customize it. To do so, click Add Request to enter the composer.

Find your key, and customize webhook action

Next to POST, add in the API endpoint we want to send our request to. You can find your Maker request url and key here, under “How to Trigger Events”

The key should look something like

https://maker.ifttt.com/trigger/{event}/with/key/XXXXXXXXXXXXXX

Replace {event} with the event name you picked earlier.

Your webhook composer should look something like this:

IFTTT allows you to send up to 3 custom data values along with your request which you can customize with liquid variables.

In the body of your request you could add something like:

Send Request

When you’re ready to test, you can click Send Request. Customer.io will show you the response from the IFTTT API.

If you’re successful, you’ll see a 200 OK. If your recipe was configured correctly, you should also have triggered it to complete!