Actionist·Qwilr
Q

Qwilr

· #446 most-used

Create, send, and close with beautiful interactive proposals

CRMSalesMarketingProductivityDocumentsFinance

Qwilr is a sales document platform that turns proposals, quotes, and contracts into interactive web pages — tracked, branded, and shareable via a single link. Connect Qwilr to Actionist and your agents can create personalised proposal pages from templates, react to buyer engagement events (first view, acceptance, publish), retrieve analytics on how prospects interact with your pricing and content, and maintain a clean document workspace on a schedule — all without anyone opening the Qwilr editor.

Try Qwilr with ActionistVisit Qwilr
Average time saved
10 hours
per person · per month
≈ 1 workdays back

Eliminates manual work. Agents eliminate the manual cycle of duplicating templates, editing variable fields, publishing pages, and tracking engagement across a Qwilr workspace — work that compounds across sales, HR, and legal at volume.

Schedule

What your Qwilr agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
Tue–Thu
Tue
Wed
Thu
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

Qwilr × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
6Apps spanned
~31 hrsSaved / week
4Personas served
For sales
Featured3 apps

Proposal auto-generated when deal reaches proposal stage

When a HubSpot deal advances to Proposal Sent, the agent fetches the contact and deal data, creates a personalised Qwilr proposal from the approved template, writes the live page URL back to the deal record, and posts the link to the #deals Slack channel — a ready-to-share proposal exists before the rep opens their email client.

~8 hrs

Time saved for your team — every week, on autopilot

The flow
Trigger·When a deal moves to Proposal Sent stage in HubSpot
Trigger
Step 1
HubSpot
Deal moves to Proposal Sent stage
read
Step 2
HubSpot
Fetch contact name, company, and deal value
write
Step 3
Q
Qwilr
Create Project from Template with deal variables
write
Step 4
HubSpot
Write Qwilr page URL back to deal record
write
Step 5
Slack
Post proposal link to #deals channel
Result
Create Project from Template with deal variablesWrite Qwilr page URL back to deal recordPost proposal link to #deals channel
The win
Saved per run
25 min
Runs / week
~20×
Every proposal is personalised and branded without manual editing
Driven bySales Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    120 min / week
    Manual proposal creation per deal

    The rep opens Qwilr, duplicates a template, manually edits the recipient name, company, and pricing, exports a link, and pastes it into the CRM — 20 to 30 minutes per proposal, every time.

    Sales Agent
    0 min
    Agent creates proposal the moment deal advances

    When a deal moves to Proposal Sent in the CRM, the agent pulls contact data, creates a personalised Qwilr page from the approved template, and writes the URL back to the deal record — before the rep opens their email.

  • Marketing
    55 min / week
    Manual campaign page creation and reporting

    The marketing team manually duplicates templates per account, edits each page, publishes individually, and pulls engagement data from the Qwilr dashboard — an hour of work at campaign launch and again each reporting cycle.

    Marketing Agent
    0 min
    Agent publishes campaign pages in batch and tracks engagement

    On campaign launch day, the agent creates and publishes all Qwilr campaign pages from templates in a single scheduled task, then retrieves weekly engagement analytics and posts a digest to the team.

  • Customer Support
    45 min / week
    Manual onboarding document creation per customer

    The CSM duplicates the onboarding template, edits the customer name, plan tier, and CSM contact details, and publishes it manually — 15 to 25 minutes per new customer.

    Customer Support Agent
    0 min
    Agent creates personalised onboarding guides automatically

    When a new customer is confirmed, the agent creates a personalised Qwilr onboarding guide from the approved template and publishes it before the first CSM call — no editing required.

  • Human Resources
    60 min / week
    Manual offer letter production per candidate

    HR opens the offer letter template, manually fills in candidate details, reviews formatting, exports a shareable link, and emails it to the hiring manager — 20 to 40 minutes per offer letter.

    Human Resources Agent
    0 min
    Agent generates offer letters at offer stage with zero editing

    When a candidate reaches offer stage, the agent creates a Qwilr offer letter from the approved HR template, embedding name, role, compensation, and start date, and stages it for hiring manager review.

  • Finance
    40 min / week
    Manual closed-won to invoice handover

    Sales marks the deal closed, emails finance with the deal details, finance manually creates the invoice record — a handover that typically takes 1 to 3 business days and frequently has data errors.

    Finance Agent
    0 min
    Agent queues invoice within a minute of proposal acceptance

    The Project Accepted webhook fires and the agent immediately logs the deal to the revenue tracker and notifies the finance team to raise the invoice — billing starts at sign-off, not when someone remembers.

  • Operations
    45 min / week
    Quarterly manual Qwilr workspace audit

    Ops manually reviews all active Qwilr pages once a quarter, identifies stale or orphaned pages, and deletes them one by one — a 2 to 3 hour task that only happens quarterly because no one has time to do it more often.

    Operations Agent
    0 min
    Agent audits and cleans the workspace weekly

    Every Monday, the agent lists all published Qwilr pages, checks engagement analytics, flags stale pages, and deletes zero-view pages older than 60 days — the workspace stays clean automatically.

  • Legal
    35 min / week
    Manual NDA and contract document creation

    Legal manually duplicates the NDA template, edits the vendor entity name and jurisdiction, exports a link, emails it to the vendor, and updates the vendor record manually — 20 to 35 minutes per NDA.

    Legal Agent
    0 min
    Agent creates and tracks NDA and contract pages automatically

    When a new vendor enters due diligence, the agent creates a Qwilr NDA page from the approved legal template, publishes it, and logs the URL to the vendor record — legal receives a notification that the document is live.

+ 100s of other Qwilr automations
Average time saved
40 hrs / person / month
Calculator

Calculate what your team saves

Team size
5 people
Hourly rate
$75 / hr
Hours saved / week
13
Hours saved / year
625
Annual ROI
$46,875

Based on Qwilr's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug Qwilr into Actionist

Pick the connection method that suits your environment.

Connect Qwilr using your account API key. All requests are authenticated with a bearer token over HTTPS to api.qwilr.com/v1.

1
Open Qwilr API Settings

Log in to Qwilr and navigate to Settings, then API & Integrations. Click Generate API Key to create a new bearer token.

2
Copy your API key

Copy the generated API key. Treat it as a password — store it in a secrets manager and do not share it in plain text.

3
Paste into Actionist

Paste the API key into Actionist and click Test connection. Actionist runs a lightweight call to verify the key before enabling any actions.

Credentials you'll need
API Key*
Qwilr → Settings → API & Integrations → Generate API Key
Actions

13 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

4 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

FAQs

Questions about Qwilr + Actionist

How does Actionist connect to Qwilr?
Go to the Apps tab, find Qwilr, and click Connect. Select API Key as the connection method. In Qwilr, navigate to Settings then API & Integrations, generate an API key, and paste it into Actionist. The agent runs a lightweight test call to confirm the handshake before any actions are executed. Once connected, the agent can create pages, monitor project events, and retrieve page data without you visiting the Qwilr dashboard.
What events from Qwilr can trigger an Actionist workflow?
The four webhook-based events Qwilr exposes are: Project Accepted (the recipient signs or accepts the document), New Project (a new page is created), Project First Viewed (the recipient opens the page for the first time), and Project Published (the page is made live and shareable). These fire within about a minute of the event occurring in Qwilr. You can chain any downstream action — CRM update, Slack alert, invoice creation — to any of these four events.
Can Actionist create a personalised Qwilr proposal from a CRM record?
Yes — the Create Project action lets you supply a template ID along with variable substitutions for the recipient's name, company, pricing figures, and any custom fields you have configured in the template. The agent pulls the relevant data from your CRM or spreadsheet, calls the Qwilr API to generate the page, and returns the shareable link. This means personalised proposals go out without anyone opening the Qwilr editor.
How can I get a Slack alert when a prospect opens my Qwilr proposal?
Project First Viewed is a webhook that fires within about a minute of the recipient opening the page for the first time. When it fires, the agent can log the view in your CRM, send a Slack notification to the account owner, and queue a follow-up task for 24 or 48 hours later — so the rep's outreach arrives when the deal is warmest. No polling required; Qwilr pushes the event.
What can Actionist do when a Qwilr project is accepted?
When the Project Accepted trigger fires, the agent can: update the deal stage in your CRM (HubSpot, Salesforce, Pipedrive), create an invoice or charge record in Xero or QuickBooks, send a congratulations message to the sales Slack channel, create an onboarding task in your project management tool, and log the signed document URL. Because Qwilr sends the accepted project details in the webhook payload, the agent has the page title, recipient, and timestamp without needing a separate lookup.
How do template variables work when creating a Qwilr page via the API?
The Create Project action accepts a template ID and a set of key-value variable pairs. The variables map to the merge fields you have set up in the Qwilr template — typically things like {{recipientName}}, {{companyName}}, {{totalPrice}}, and line-item rows. You define these in the Qwilr template editor; the agent populates them at creation time. If a variable is missing from the payload, Qwilr leaves the merge field blank rather than erroring, so verify your data mapping before enabling the workflow at volume.
Does the Project First Viewed trigger fire every time someone views the page?
Because Qwilr pages are web pages, the same shared URL can be opened multiple times. Project First Viewed fires only on the first open — it does not fire again if the same recipient (or another person) opens it later. If you need to track every subsequent view, use Qwilr's built-in analytics dashboard or poll the Get Project action on a scheduled task to check the view count. The webhook gives you the warm-lead signal on first contact; the analytics dashboard gives you the full engagement picture.
Is the Qwilr API connection secure?
The Qwilr API uses bearer token authentication. All requests go over HTTPS to api.qwilr.com/v1. The API key grants access to your entire Qwilr workspace, so treat it like a password: store it in Actionist's encrypted credentials store (not in a plain-text config), rotate it if a team member with access leaves, and generate a fresh key if you suspect exposure. Actionist stores credentials encrypted at rest and never logs them in plain text.