Send a Customer.io update when a compliance deadline needs customer attention
Turn a confirmed compliance deadline into a clear customer update, without rebuilding the audience and message by hand.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Trigger Broadcast
Tool to manually trigger a broadcast. use when you need to override the default audience and provide personalization data after confirming the broadcast id.
Why this helps
A deadline can require a customer update, but switching from compliance tracking to campaign setup makes it easy to delay or miss the message.
- Send an update promptly after a deadline event reaches the webhook.
- Reuse a confirmed broadcast and the personalization data supplied with the event.
- Keep the compliance event and its customer communication in one automation flow.
Setup
Build it in a few focused steps.
- 1Connect 21risk and Customer.io once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one plain-language instruction, tell Notis to trigger the supplied Customer.io broadcast using the broadcast ID and personalization data in the webhook, after confirming the deadline event is valid.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real deadline example that includes a valid broadcast ID and personalization data.
Questions about this workflow
What starts this automation?
A webhook request starts it. Configure the caller to send a confirmed compliance deadline event with the needed broadcast ID and personalization data.
Does this create a Customer.io broadcast?
No. Customer.io's Trigger Broadcast action runs an existing broadcast. Supply a valid broadcast ID and confirm the audience and content before testing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 21risk to Customerio. A trigger fires from one place; an action lands in another.
21risk triggers
Customerio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Suppress Customer Profile
Tool to suppress a person. use when you need to permanently delete a customer's profile and prevent them from being re-added.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Integrations
Tool to retrieve a list of integrations in your workspace. use when you need to discover configured integrations.
Get Messages
Tool to retrieve a list of messages sent from your workspace. use when you need paginated delivery metrics for messages, e.g., list email messages delivered between two timestamps.
Get Segment Details
Tool to retrieve details of a specific segment. use after identifying the segment id from list segments.
Get Segment Membership
Tool to retrieve people in a specific segment. use when you need to page through segment membership after identifying segment id.
Get Segments
Tool to retrieve a list of segments in your workspace. use when you need to fetch all segments after configuring segment rules.
Get Trigger
Tool to retrieve details about a specific trigger. use after triggering a broadcast to confirm its status and metadata.
Get Triggers
Tool to retrieve a list of triggers for a specific broadcast. use after identifying broadcast id to inspect associated triggers.
Connect any two apps with Notis in the middle.
21risk and Customerio, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Customerio.