Carry unsubscribe requests into BigMailer
Let Algodocs extract the request details, then have Notis update the identified BigMailer contact’s unsubscribe status. Review a real example before relying on the automation.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Contact
Updates a BigMailer contact’s details, fields, lists, and unsubscribe settings.
Why this helps
Unsubscribe requests buried in forms or documents can be easy to overlook when someone has to find and update each contact manually.
- Bring processed unsubscribe requests into the contact workflow.
- Reduce manual searching for the contact to update.
- Use the request’s stated intent as the condition for an update.
Setup
Build it in a few focused steps.
- 1Connect Algodocs and BigMailer once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis to update the identified BigMailer contact to unsubscribe only when the processed request clearly asks to stop marketing emails.
- 4Choose the Webhook trigger and select where run reports should go.
- 5Send one real unsubscribe request example to the Webhook and review the run report.
Questions about this workflow
Does the workflow identify contacts from a document by itself?
Algodocs can extract document data, but the listed BigMailer update action operates on an existing contact. Include enough identifying information in the request for Notis to identify the contact, and verify the match in a real run.
What happens if the request is unclear?
Tell Notis to skip the update and report the ambiguity. Do not infer unsubscribe intent from a general complaint or unrelated document.
Does Algodocs have a native trigger for these requests?
No Algodocs trigger is listed. An HTTP request to the Notis Webhook starts this workflow.
When this happens · Trigger
Do this · Action
Updates a BigMailer contact’s details, fields, lists, and unsubscribe settings.
Supported Triggers and Actions
Notis builds workflows that link Algodocs to Bigmailer. A trigger fires from one place; an action lands in another.
Algodocs triggers
Bigmailer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Transactional Campaign
Creates a transactional email campaign for a brand.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Brand
Creates a brand for organizing campaigns and default sending settings.
Get User Information
Retrieves information about the authenticated user.
Create Brand Property
Creates a custom brand property for use in email templates.
List All Brands
Lists brands in the authenticated BigMailer account.
Create Bulk Campaign
Creates a bulk email campaign for immediate sending or scheduling.
Create Contact
Creates a contact within a brand, with optional list membership and subscription status.
Create Contact Batch
Uploads 1 to 1,000 contacts for asynchronous creation or update in a BigMailer brand.
Connect any two apps with Notis in the middle.
Algodocs and Bigmailer, 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 Bigmailer.