If a webhook is triggered, get a mobile notification
How this automation works
Add people to Customer.io segments automatically. This runs whenever your Webhooks event receives a web request with a JSON payload and adds the specified person to the selected manual segment in Customer.io. It's ideal for sending leads, signups, or external user updates from your service into Customer.io to trigger segment-based campaigns and automation.
If
Trigger ingredients
EventName
JsonPayload
OccurredAt
Then
Action fields
person_identifier
manual_segment
Services used in this Applet
You might also like...
View more Applets
Related services
Create your own Webhooks and Customer.io workflow
Create custom workflows effortlessly by selecting triggers, queries, and actions. With IFTTT, it's simple: “If this” trigger happens, “then that” action follows. Streamline tasks and save time with automated workflows that work for you.
15 triggers, queries, and actions
Person entered a segment
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when a person becomes a member of a segment you choose in Customer.io.
Receive a web request
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
This trigger fires every time the Maker service receives a web request to notify it of an event. For information on triggering events, go to your Maker service settings and then the listed URL (web) or tap your username (mobile)
Receive a web request with a JSON payload
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
This trigger fires every time the Maker service receives a web request to notify it of an event. For information on triggering events, go to your Maker service settings and then the listed URL (web) or tap your username (mobile)
History of web requests received
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times when the Maker service received a web request to notify it of an event. For information on querying events, go to your Maker service settings and then the listed URL (web) or tap your username (mobile)
Look up a person
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a person's attributes and segment memberships from Customer.io.
Make a web request
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the status code from a request made to the provided URL. If the response body is in the correct format it will also return the body’s extracted values. Please see the documentation link on the Webhooks service page.
Make a web request with JSON response
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the JSON response body. You can use filter code to parse it. Please see the documentation link on the Webhooks service page.
Add a person to a segment
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will add a person to one of your manual segments in Customer.io.
Create or update a person
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will create a person in Customer.io, or update them if they already exist, setting the attributes you provide.
Make a web request
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will make a web request to a publicly accessible URL. NOTE: Requests may be rate limited.
Remove a person from a segment
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will remove a person from one of your manual segments in Customer.io.
Send a transactional message
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will send a transactional message to a person using a transactional message template you have set up in Customer.io.
Suppress a person
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will suppress a person in Customer.io so they stop receiving messages.
Track an event
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will record a custom event for a person in Customer.io, which can start or advance that person's journeys and campaigns.
Trigger a broadcast
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will trigger an API-triggered broadcast in Customer.io so it sends to its configured audience.
Add a person to a segment
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will add a person to one of your manual segments in Customer.io.
Create or update a person
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will create a person in Customer.io, or update them if they already exist, setting the attributes you provide.
History of web requests received
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times when the Maker service received a web request to notify it of an event. For information on querying events, go to your Maker service settings and then the listed URL (web) or tap your username (mobile)
Look up a person
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a person's attributes and segment memberships from Customer.io.
Make a web request
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the status code from a request made to the provided URL. If the response body is in the correct format it will also return the body’s extracted values. Please see the documentation link on the Webhooks service page.
Make a web request
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will make a web request to a publicly accessible URL. NOTE: Requests may be rate limited.
Make a web request with JSON response
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the JSON response body. You can use filter code to parse it. Please see the documentation link on the Webhooks service page.
Person entered a segment
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when a person becomes a member of a segment you choose in Customer.io.
Receive a web request
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
This trigger fires every time the Maker service receives a web request to notify it of an event. For information on triggering events, go to your Maker service settings and then the listed URL (web) or tap your username (mobile)
Receive a web request with a JSON payload
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
This trigger fires every time the Maker service receives a web request to notify it of an event. For information on triggering events, go to your Maker service settings and then the listed URL (web) or tap your username (mobile)
Remove a person from a segment
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will remove a person from one of your manual segments in Customer.io.
Send a transactional message
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will send a transactional message to a person using a transactional message template you have set up in Customer.io.
Build an automation in seconds!
If
Select a trigger the automation will use
Then
Select an action the automation will perform
You can add delays, queries, and more actions in the next step!
More on Webhooks and Customer.io
About Webhooks
Learn to use webhooks and integrate other services on IFTTT with your DIY projects. You can create Applets that work with any device or app that can make or receive a web request. If you'd like to build your own service and Applets, check out the IFTTT Developer Dashboard. Connect a webhook to any of the 750+ apps and services on IFTTT.
Learn to use webhooks and integrate other services on IFTTT with your DIY projects. You can create Applets that work with any device or app that can make or receive a web request. If you'd like to build your own service and Applets, check out the IFTTT Developer Dashboard. Connect a webhook to any of the 750+ apps and services on IFTTT.
About Customer.io
Customer.io is a customer engagement platform that helps marketing and lifecycle teams turn customer data into personalized messages across email, SMS, push, in-app, and other channels. Use it on IFTTT to feed real-world activity into Customer.io, manage segments, and trigger messages. Visit customer.io.
Customer.io is a customer engagement platform that helps marketing and lifecycle teams turn customer data into personalized messages across email, SMS, push, in-app, and other channels. Use it on IFTTT to feed real-world activity into Customer.io, manage segments, and trigger messages. Visit customer.io.