Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Qwilr

Create beautiful, interactive sales documents and proposals with Qwilr. Automate page creation, track views, and handle acceptance events.

CategorySales And Crm
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Qwilr with Flows360

Create beautiful, interactive sales documents and proposals with Qwilr. Automate page creation, track views, and handle acceptance events.

Use the Qwilr connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 2 actions and 7 triggers.

Available actions

  • Create Page
  • Custom API Call

Available triggers

  • Page Accepted
  • Page Partially Accepted
  • Page Preview Accepted
  • Page Viewed
  • Page First Viewed
  • Page Set Live
  • Plus 1 additional declared trigger.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Qwilr
  • Package: @activepieces/piece-qwilr@0.2.0
  • Exact artifact digest: sha256:59506f9d4db3d25cd87b7ca5a906ed349f91da6f34b638444deecfab2ddfcc87
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Page (create_page), Creates a new Qwilr page from saved blocks or template. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Page Accepted, webhook.
  • Page Partially Accepted, webhook.
  • Page Preview Accepted, webhook.
  • Page Viewed, webhook.
  • Page First Viewed, webhook.
  • Page Set Live, webhook.
  • Page Revived Live, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects9
Supported actions2
Triggers7

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Page Yes No Creates a new Qwilr page from saved blocks or template.
Custom API Call Yes No Make a custom API call to a specific endpoint
Page Accepted Yes No webhook trigger declared by the pinned package.
Page Partially Accepted Yes No webhook trigger declared by the pinned package.
Page Preview Accepted Yes No webhook trigger declared by the pinned package.
Page Viewed Yes No webhook trigger declared by the pinned package.
Page First Viewed Yes No webhook trigger declared by the pinned package.
Page Set Live Yes No webhook trigger declared by the pinned package.
Page Revived Live Yes No webhook trigger declared by the pinned package.

Supported actions

Create Page · Read

Creates a new Qwilr page from saved blocks or template.

create_page · Risk: low · Retry: safe

Inputs

  • templateId · string · Required, ID of the template to use for the page
  • name · string · Optional, Title of the page, visible as the browser page title
  • published · boolean · Optional, Whether the page is publicly available; false means the page will be in Draft status
  • ownerId · string · Optional, ID of the user that should own the page. If not specified, the owner of the access token will be the owner of the page.
  • tags · array · Optional, The tags for your page. Tags are case-sensitive.
  • metadata · object · Optional, Data you provide, that will be returned as part of all Webhooks.
  • substitutions · object · Optional, Mapping of token API reference keys to substitution values used throughout the page.
  • acceptSettings · object · Optional, Configures settings for the accept block in the template being used. Only relevant if you have an accept block.
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

Page Accepted · Webhook

Triggers when a Qwilr page is accepted

Page Partially Accepted · Webhook

Triggers when a Qwilr page is partially accepted

Page Preview Accepted · Webhook

Triggers when a Qwilr page preview is accepted

Page Viewed · Webhook

Triggers when a Qwilr page is viewed

Page First Viewed · Webhook

Triggers when a Qwilr page is viewed for the first time

Page Set Live · Webhook

Triggers when a Qwilr page is set to live

Page Revived Live · Webhook

Triggers when a Qwilr page is revived to live status

Setup

Setup

  1. Add the Qwilr connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-qwilr@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 2 actions and 7 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Qwilr connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-qwilr@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com