Check available templates for an incoming document request
Give a document request a quick check against the templates DocuGenerate actually has available.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get or list templates
Retrieves or lists existing templates.
Why this helps
A document request can stall when no one knows which template exists or what it is called.
- Retrieve current template metadata before selecting a document format.
- Avoid relying on remembered or assumed template names.
- Surface available choices as part of an incoming request.
Setup
Build it in a few focused steps.
- 1Connect Abuselpdb and DocuGenerate once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3Describe that each request should retrieve the available DocuGenerate templates and report the options, using any supplied Abuselpdb context where relevant.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real request and confirm the returned template options.
Questions about this workflow
Does this generate a document?
No. It retrieves template listings and metadata. Use a separate generation workflow once you have selected a template and supplied its data.
Why is Abuselpdb included in this workflow?
The source app has no trigger events, so the HTTP request starts the workflow. Any relevant IP or abuse context must be supplied in the request or fetched from Abuselpdb.
Can the workflow use a template ID that was not returned?
It should only use an ID confirmed by DocuGenerate. This workflow retrieves available templates for that purpose.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abuselpdb to Docugenerate. A trigger fires from one place; an action lands in another.
Abuselpdb triggers
Docugenerate actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Generate documents from template
Generates documents by merging data into a template.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Document
Permanently deletes a document from storage.
Delete template
Permanently deletes a template and all its stored versions.
Update Document
Renames an existing generated document.
Get document by ID
Retrieves a document’s details and download link by ID.
Get or list templates
Retrieves or lists existing templates.
Get template by ID
Retrieves a template’s details by ID.
Update Template
Updates a template’s file and settings.
Connect any two apps with Notis in the middle.
Abuselpdb and Docugenerate, 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 Docugenerate.