Create beautiful, interactive sales documents and proposals with Qwilr. Automate page creation, track views, and handle acceptance events.
Qwilr currently provides 7 triggers that can start a workflow and 2 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Page Accepted
Triggers when a Qwilr page is accepted
Page Partially Accepted
Triggers when a Qwilr page is partially accepted
Page Preview Accepted
Triggers when a Qwilr page preview is accepted
Page Viewed
Triggers when a Qwilr page is viewed
Page First Viewed
Triggers when a Qwilr page is viewed for the first time
Page Set Live
Triggers when a Qwilr page is set to live
Page Revived Live
Triggers when a Qwilr page is revived to live status
Create Page
Creates a new Qwilr page from saved blocks or template.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Qwilr event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Page Accepted
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Qwilr action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Page
Combine Qwilr with another integration and Coherence records to keep account, contact, and deal context attached to the work around it.
Starts with
Page Accepted
Finishes with
Create Page, then preserve the outcome in Coherence
The exact authentication fields depend on Qwilr. The workflow structure stays straightforward:
Authorize the Qwilr account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Qwilr or provide a complementary trigger or action.
Qwilr currently provides 7 triggers that can start a workflow and 2 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Qwilr currently lists 7 triggers and 2 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Qwilr triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
