Retrieve the Docmosis API key for an authorized workflow
When an authorized workflow needs the Docmosis Bearer token, Notis can retrieve it from connection metadata as part of the run.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Docmosis: Get API Key
Retrieve the API access key from connection metadata.
Why this helps
A multi-step API workflow can stall when it needs the connected Docmosis authorization token before calling another service action.
- Retrieve the access token from the existing Docmosis connection metadata.
- Support an authorized workflow that needs the Bearer token before other API calls.
- Avoid manually looking up the connection value during that run.
Setup
Build it in a few focused steps.
- 1Connect Ai ml api and Docmosis once in the Notis portal.
- 2Create an automation in the portal or by telling Notis what you want it to do.
- 3In one instruction, ask Notis to retrieve the Docmosis API access key from connection metadata for the authorized workflow that needs it.
- 4Pick the notis_webhook trigger and choose where run reports should go.
- 5Test with the intended authorized workflow and confirm it can proceed to its next supported step.
Questions about this workflow
Where does the key come from?
The action extracts the Docmosis API access key from the Docmosis connection metadata, specifically the Bearer token in the Authorization header.
Should the token be included in a general run report?
Keep the workflow report focused on whether retrieval succeeded and avoid exposing the token in broadly visible report channels.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Ai ml api to Docmosis. A trigger fires from one place; an action lands in another.
Ai ml api triggers
Docmosis actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Docmosis: Delete Image(s)
Delete one or more stored images.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Docmosis: Delete Template(s)
Delete one or more templates from the environment.
Docmosis Environment Ready
Check whether the environment is active and within quota.
Docmosis Environment Summary
Retrieve the environment’s status, plan, and quota summary.
Docmosis: Get API Key
Retrieve the API access key from connection metadata.
Get Batch Upload Status
Check the progress or completion status of a template batch upload.
Download Docmosis Images
Download stored image files.
Get Docmosis Render Queue
Retrieve the current render queue status and usage.
Connect any two apps with Notis in the middle.
Ai ml api and Docmosis, 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 Docmosis.