Keep customer profiles current with document data
When a document is processed, let Algodocs extract the details and have Notis update the matching Customer.io profile, without copying information between tools by hand.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Identify Person
Creates or updates a Customer.io person profile and assigns traits.
Why this helps
Document details can sit in a separate system while customer profiles stay out of date, leaving your team to copy and verify the same information twice.
- Update an existing Customer.io profile or create one when it does not yet exist.
- Keep document status and selected business attributes alongside the customer record.
- Avoid manually retyping extracted details.
Setup
Build it in a few focused steps.
- 1Connect Algodocs and Customer.io once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, tell Notis to use Algodocs to extract and classify the document, then update the matching Customer.io profile with only the attributes you specify.
- 4Pick the Webhook trigger and choose where run reports should go.
- 5Test with one real document and a matching customer identifier.
Questions about this workflow
What starts this automation?
An HTTP request starts the Notis Webhook. Configure the system that processes or receives the document to call it when the document is ready.
How does Notis find the right profile?
Tell Notis which identifier to use, such as the customer's email or user ID, and make sure the document or request includes it.
Can I choose which document details are saved?
Yes. Name the attributes you want in your instruction. Keep sensitive document contents out of the profile unless you have a clear need and permission to store them.
When this happens · Trigger
Do this · Action
Creates or updates a Customer.io person profile and assigns traits.
Supported Triggers and Actions
Notis builds workflows that link Algodocs to Customer.io. A trigger fires from one place; an action lands in another.
Algodocs triggers
Customer.io 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 Customer.io group and can include group traits.
Get Integrations
Retrieves the configured integrations in your Customer.io workspace.
Create Profile Alias
Creates an alias to merge two Customer.io profiles.
Author, Version, and Publish Email
Updates and versions a linked Design Studio email, then publishes it live in its workflow for all languages.
Get Messages
Retrieves messages sent from your workspace and their delivery metrics.
Get Segment Details
Retrieves details about a specific segment.
Create Segment
Creates an empty manual segment in Customer.io.
Connect any two apps with Notis in the middle.
Algodocs and Customer.io, or any other combination from 1,600+ 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 Customer.io.