Handle opt-out cleanup with a clear record check
Turn an opt-out notice into a controlled AppDrag cleanup request, using the identity details you supply and keeping the run outcome visible.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Execute Cloud Backend function via DELETE
Executes a cloud backend function in the default environment.
Why this helps
Opt-out updates can leave related application records active if cleanup depends on someone remembering a separate manual step.
- Reduce manual cleanup after an opt-out notice.
- Make record identity checks part of the instruction.
- Keep a report of the delete call and any missing identifiers.
Setup
Build it in a few focused steps.
- 1Connect ActiveCampaign and AppDrag once in the Notis portal.
- 2Create an automation for opt-out cleanup.
- 3Tell Notis to verify the supplied record identifier and call your AppDrag DELETE function only for a confident match.
- 4Choose the webhook trigger and where run reports go.
- 5Test with one real opt-out example and confirm the intended AppDrag record is removed.
Questions about this workflow
How does an opt-out reach this workflow?
The Notis webhook starts when it receives an HTTP request. Configure the relevant ActiveCampaign event to send the needed opt-out details to that webhook.
What does the DELETE action do?
It executes an AppDrag Cloud Backend function via DELETE on the default environment. That function's behavior depends on its configuration.
Can it delete without a record identifier?
Your instruction should require a reliable identifier and have Notis report missing or ambiguous identity details without calling the delete function.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Active campaign to Appdrag. A trigger fires from one place; an action lands in another.
Active campaign triggers
Appdrag actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Execute Cloud Backend function via DELETE
Executes a cloud backend function in the default environment.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Execute Preprod Function (DELETE)
Executes a backend function in the preproduction environment for testing or validation.
Execute PROD API Function (GET)
Executes a backend function in the production environment.
Execute Dev Function (PATCH)
Executes a backend function in the development environment.
Execute Cloud Backend function via POST
Executes a cloud backend function in the default environment.
Execute Function POST (Preprod Env)
Executes a cloud backend function in the preproduction environment.
Execute Cloud Backend function via PUT (default)
Executes a cloud backend function in the default environment.
Execute Cloud Backend function via PUT (preprod)
Executes a cloud backend function in the preproduction environment.
Connect any two apps with Notis in the middle.
Active campaign and Appdrag, 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 Appdrag.