Post Customer.io person profile to Slack
by
3 ready-made Customer.io and Webhooks Applets
Turn one on, or build your own. Customer.io can start an automation with "Person entered a segment", and IFTTT can then run "Make a web request" on Webhooks.-
-
-
Send Webhooks when Customer.io person enters segmentby
-
-
Add a person to Customer.io when Webhooks receives eventby
-
Automate Customer.io and Webhooks from your AI assistant
Ask Perplexity to create Customer.io applets for you, right from your AI assistant, with IFTTT MCP.
Set up IFTTT MCP
Create your own Customer.io and Webhooks 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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when a person becomes a member of a segment you choose in Customer.io.
Receive a web request
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires every time the Webhooks service receives a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
Receive a web request with a JSON payload
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires every time the Webhooks service receives a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
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 the Webhooks service received a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
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 the Webhooks service received a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
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 hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires when a person becomes a member of a segment you choose in Customer.io.
Receive a web request
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires every time the Webhooks service receives a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
Receive a web request with a JSON payload
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every hour on Free, every 15 minutes on Starter, and every 5 minutes on Pro and Pro+.
This trigger fires every time the Webhooks service receives a web request to notify it of an event. To find your webhook URL and key, open Documentation on the Webhooks service page (mobile: Account > My services > Webhooks).
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
Person entered a segment
Receive a web request
Receive a web request with a JSON payload
Then
Select an action the automation will perform
Add a person to a segment
Create or update a person
Make a web request
Remove a person from a segment
Send a transactional message
Suppress a person
Track an event
Trigger a broadcast
You can add delays, queries, and more actions in the chat.
GET STARTED
How to connect to a Customer.io automation
Find an Applet using Customer.io and Webhooks
Find an automation to connect to, or create your own!Connect IFTTT to your accounts
Securely connect the Applet services to your respective accounts.Finalize and customize your Applet
Review trigger and action settings, and click connect. Simple as that!Make more happen with your credits
-
More credits, more possibilities
Get more credits per month to power more automation activity. -
Power more advanced automations
Use credits to power your automations, including actions that require more processing. -
Access faster speeds and higher rate limits
Get faster updates and more actions with increased rate limits and more frequent checks.
Customer.io and Webhooks tips, tools, and resources
More on Customer.io and Webhooks
About Customer.io
Customer.io and IFTTT let you automatically add people to segments, track events, and send messages based on real-world activity.
About Webhooks
Webhooks and IFTTT let you connect any device or app that speaks HTTP to over 1000 services, creating automations between your custom projects and the apps you use.