Handle unsubscribe requests with the right contact context
Send an unsubscribe request and delivery identifier to a Notis webhook. Addressfinder checks the submitted contact details before Customer.io processes the request.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Unsubscribe from Delivery
Unsubscribes a person from email by setting their unsubscribed status to true.
Why this helps
Manually resolving an unsubscribe request can take time and risks applying it to the wrong person or delivery.
- Check the submitted contact details before acting on a request.
- Apply the custom unsubscribe to a specific delivery when the required identifiers are provided.
- Keep a clear run report for reviewing request handling.
Setup
Build it in a few focused steps.
- 1Connect Addressfinder and Customer.io once in the Notis portal.
- 2Create an automation in Automations, New Automation, and describe how to validate an unsubscribe request before applying it.
- 3Choose a webhook trigger and include the contact details, Customer.io person identifier, and delivery identifier.
- 4Choose where Notis should send run reports.
- 5Test with one valid request and confirm the intended person is unsubscribed from the specified delivery.
Questions about this workflow
Does this unsubscribe someone from all email?
The selected action handles a custom unsubscribe request attributed to a specific delivery. It is not described as a global suppression action.
What identifiers are needed?
Provide enough information to identify the person and the delivery, along with the contact details to check.
What if the contact check fails?
Describe in the automation instruction that uncertain or failed checks should be reported for review rather than applied.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Addressfinder to Customerio. A trigger fires from one place; an action lands in another.
Addressfinder triggers
Customerio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Suppress Customer Profile
Permanently deletes a customer profile and prevents it from being added again; this action is irreversible.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Person to Group
Adds a person to a group, linking them to an organization, account, or project.
Get Integrations
Lists the integrations configured in your workspace.
Create Profile Alias
Merges one profile into another, moving its data to the canonical profile.
Get Messages
Retrieves messages sent from your workspace and their delivery metrics.
Get Segment Details
Retrieves details about a specific segment.
Get Segment Membership
Retrieves the people in a specific segment.
Get Segments
Lists the segments in your workspace.
Connect any two apps with Notis in the middle.
Addressfinder 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.