See signing progress alongside your CMS campaign
Get a scheduled view of relevant Docuseal submissions so follow-up does not depend on remembering to check each request.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Submissions
Lists existing document submissions.
Why this helps
Signature requests can remain pending because their status is spread across a separate tool from the campaign context.
- Review Docuseal submissions on a recurring schedule.
- Summarize relevant status for a campaign you identify in Agility CMS.
- Make follow-up needs visible in a run report.
Setup
Build it in a few focused steps.
- 1Connect Agility CMS and Docuseal once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis in plain language from any channel.
- 3In one instruction, identify the CMS campaign and tell Notis how to identify relevant Docuseal submissions and summarize their statuses.
- 4Pick the notis_cron trigger and choose where run reports go.
- 5Test with one real campaign and verify the report covers the intended submissions.
Questions about this workflow
Does the CMS provide signing status?
No. This workflow reads submission data from Docuseal and uses the CMS campaign as context.
Can the workflow guarantee it finds every campaign submission?
Only if your instruction provides a reliable way to identify them, such as a document filter or other available identifier. Do not assume an association exists.
Does it send reminders to signers?
No. It reports status. A separate action would be needed to update a submitter or resend a request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agility cms to Docuseal. A trigger fires from one place; an action lands in another.
Agility cms triggers
Docuseal actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Archive Template
Archives a template.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Archive Submission
Archives a submission, which can be restored and is not permanently deleted.
Create Submission From PDF
Creates and sends a one-off PDF submission for electronic signature.
Clone Template (v2)
Clones an existing template into a new template.
Create Template from HTML
Creates a fillable document template from HTML.
Create Submission
Creates and sends signature requests from an existing template.
Get Template
Retrieves a template’s details.
Create Submissions From Emails
Creates a submission for a template and sends each recipient a unique signing link.
Connect any two apps with Notis in the middle.
Agility cms and Docuseal, 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 Docuseal.