Governed workflow templates
Install ready-made workflows that arrive as drafts with approval policies on every write, built-in safeguards and suggested checks.
Updated 11/10/2026
On this page
- What a template installs
- Safeguards in every template
- Find a template
- Try one in the sandbox
- The templates
- Use-case templates
- Care visits to draft QuickBooks invoices
- Candidate screening summaries
- Contracts to draft DocuSign envelopes
- Commerce low stock to purchase requests
- Qualified leads to accounting customers
- Install a template
- Next
What a template installs
Governed workflow templates are ready-made Connect integrations designed with real businesses. Open Connect → Templates to browse them. Installing one creates:
Draft flows with compiler-ready steps and field mappings. Nothing runs until you review and publish them.
Approval policies for every write the flows make, applied to the connections you choose.
Suggested checks you can add to each flow's check suite before release (see Checks and release gates).
Safeguards in every template
Every write waits for a person. Messages are drafts, or need approval to send.
Nothing moves money. Payments, refunds, transfers and deletes are never used, and Nexra refuses them at risk tier R4 whatever a policy says.
Policies only tighten. An active deny or approval policy already on a connection is kept exactly as it is. A missing, switched-off or allow policy becomes the template's approval policy. If an existing allow policy carries its own limits or grant requirement, installation stops and asks you to combine the two by hand, so nothing is ever loosened.
Built on real operations. Every step names an operation and fields Nexra actually serves, and this is tested on every release.
Each template page lists its Built-in safeguards (what it guarantees never to do) and Setup notes (practical points for installing and running it).
Find a template
Open Connect → Templates. The gallery groups templates by what they help with, and the filter row at the top shows one group at a time:
| Group | For example |
|---|---|
| Payments and finance | Settlements booked as journals, a virtual account per invoice, overdue reminders |
| Commerce and B2B | Trading partners on two ERPs, cross-border orders, low stock to purchase requests |
| Energy and utilities | Meter to cash, supply interruption notices, billing disputes |
| People | Evidence-based screening, new starters |
| Legal | Contract obligations, contracts to signature |
| Customer relationships | Industry signals to opportunities, purchase to campaign, delivery problems |
| Operations | Abnormal readings, morning numbers, prescriptions to pharmacy |
You don't need to know a template's name. Ask Nexra Agent in your own words, for example "book Flutterwave settlements in NetSuite" or "remind us before contract obligations are due". It matches the systems, the task and the industry you mention, shows the best matches first, explains the one you pick and prepares the install for you to approve.
Try one in the sandbox
Try a template before you use it for real:
Open the Nexra Sandbox workspace from the workspace switcher.
Connect the systems the template uses with test (sandbox) credentials, your own keys for each provider.
Install the template. Its flows arrive as drafts with approval on every write.
Publish a flow and run it against the test connections, or upload the template's sample file where it takes one. Approve the writes it proposes and check the results in each system.
When you are happy, install it in your own workspace and connect your live accounts. Going live needs a tested version and a second person's approval (see Approvals and deployments).
The templates
| Template | What it does | Systems |
|---|---|---|
| Care visits to draft QuickBooks invoices | Turns approved care visit lines into one QuickBooks invoice per line, created unsent once a finance approver accepts it. | One Touch Health, an approved visit export (upload or signed webhook) or a FHIR R4 health record system, QuickBooks Online |
| Candidate screening summaries | Sends the hiring panel a brief for each open role, and a factual summary for every candidate on your approved CV list. | SeamlessHR, your CV list, Microsoft 365 (Outlook drafts or Teams) |
| Contracts to draft DocuSign envelopes | Proposes a draft envelope from your DocuSign template for each opportunity or document ready for signature. Legal approves every draft. | Dynamics 365 Sales or SharePoint, DocuSign |
| Commerce low stock to purchase requests | Proposes a purchase request for each product at or below its reorder point, or for each line of a provider-signed order. | Magento, VTEX, Shopify or Adobe Commerce; Xero, Business Central or Jira |
| Qualified leads to accounting customers | Turns each sales-qualified lead with an e-mail address into a proposed accounting customer. | HubSpot or Dynamics 365 Sales; QuickBooks Online or Xero |
Use-case templates
Every use-case story on the Nexra website has a template you can install in the Nexra Sandbox and try with sample data. Each installs as governed drafts (at most three flows per choice) with approval on every write. Recording a payment that has already arrived, for example against an invoice, is a bookkeeping write and always needs approval; no template starts, sends or refunds a payment.
| Category | Template | What it does |
|---|---|---|
| Payments and finance | Payment provider settlements booked as balanced journals | Books each Flutterwave, Paystack or Stripe settlement in NetSuite, Business Central, Sage, Xero or QuickBooks as one balanced journal (net, fees, VAT on fees, refunds, chargebacks and charges against gross). Held or unbalanced settlements go to review. |
| Payments and finance | A virtual account for every B2B invoice | Creates a Monnify invoice and virtual account per invoice, records exact payments against the NetSuite or Xero invoice, and sends overpayments, underpayments and late payments to review. |
| Payments and finance | Marketplace split settlements reconciled per seller | Books each Paystack split settlement against the right seller's payable. |
| Payments and finance | Overdue invoice reminders | One reminder per overdue invoice from your aged debtors export, as a Gmail or Outlook draft or an approved WhatsApp message. |
| Payments and finance | Payments from buyers abroad recorded in the books | Records foreign-currency Flutterwave or Paystack payments in QuickBooks. |
| Payments and finance | Affordability review from bank data | Requests Mono statement insights and puts a bank data summary on the Salesforce application for an analyst. |
| Payments and finance | Finance answers in Microsoft Teams | Posts cash by bank account and receivables by age from Xero or QuickBooks to the finance channel each morning. |
| Commerce and B2B | Trading partners on two ERPs | Keeps a supplier on Business Central and a buyer on NetSuite in step: customer, prices and stock, orders, shipping status, invoices and payments, each side approving writes into its own ERP. |
| Commerce and B2B | Cross-border orders shipped and booked | Ships paid Shopify orders going abroad with DHL Express and records every paid order in Xero in its own currency. |
| Energy and utilities | Gas distribution meter to cash | Bills metered volumes at the contract tariff, flags unbilled days, tariff errors and short payments, and drafts monthly volume statements. |
| Energy and utilities | Supply interruption notice to affected customers | Approved email or SMS to every affected customer, with a HubSpot case on each. |
| Energy and utilities | Gas billing dispute pack to resolution | An evidence pack checklist on each dispute ticket, then the decided credit posted to the ERP after finance approval. |
| People | Evidence-based candidate screening | An evidence matrix per candidate (evidenced with a quote, or not evidenced in the supplied CV), clarification questions and a mandatory recruiter review task. Nothing is rejected. |
| Legal | Contract obligations tracker with reminders | Logs signed DocuSign contracts and each obligation (owner, due date, source clause, status, reminder lead time) to SharePoint, with Outlook reminders. |
| Customer relationships | Industry signal to qualified opportunity | An account brief that keeps evidence apart from assumptions, a Salesforce opportunity, a PandaDoc proposal draft and a follow-up that stops when the customer replies or the owner pauses it. |
| Customer relationships | Every purchase starts the next campaign | Paid Shopify orders to Segment and Klaviyo. |
| Customer relationships | Delivery problems reach support with the full picture | Delivery exceptions from AfterShip become Zendesk tickets with the order and tracking details. |
| Operations | Abnormal reading to engineering review and work order | Read-only readings from Cognite Data Fusion open a ServiceNow review ticket; a work order is proposed only after engineering asks for one. |
| Operations | Start every day with the numbers | Stripe balance and who is out today from HiBob, posted to Slack or Teams. |
| Operations | Prescriptions from hospital to pharmacy | A pharmacist dose-check task for each prescription and an approved text when it is ready. |
Each template's page lists what it does, its safeguards, its setup notes and anything it leaves to you.
Care visits to draft QuickBooks invoices
Choose how visit lines arrive: an uploaded CSV or JSON export (the default), a signed webhook from your rostering system, or a reviewed REST export. Only lines marked approved are invoiced, and each client is matched to its QuickBooks customer through a reviewed match table.
If your health record system offers a FHIR R4 API, choose Finished visits from my health record system instead: once a day Nexra reads the visits finished since the last run (only their ID, patient reference, visit type and times), prices each from your visit-type price table and proposes one invoice per visit. The connection asks only for permission to read visits, run details are hidden and kept for a short time, and nothing is shown to an AI model unless your workspace allows it.
Safeguards: never sends, e-mails or shares invoices, takes payment or runs payroll. Clinical notes, addresses, dates of birth and contact details are never read or copied, and an export carrying them is refused rather than stored. An unmatched client stops that line; Nexra never guesses a customer.
Default policies: invoices.create and customers.create need an Approver, with at most 200 per run. Invoices above £2,500 are refused.
Setup notes: each upload takes up to 20 MiB and 10,000 lines, each webhook delivery up to 500 lines. To keep items out of accounts receivable until finance converts them, switch the destination to estimates.create.
Candidate screening summaries
Open roles come from SeamlessHR. Candidate summaries are built only from the fields on your approved CV list (role, current role, experience, skills, qualifications, location, recruiter notes and the CV link), so reviewers see exactly the facts you supplied.
Safeguards: every candidate gets a summary; none is rejected, scored, ranked or filtered out. SeamlessHR is read-only. Outlook output is always a draft for the hiring manager to send. Protected characteristics such as age, gender, nationality, photos and date of birth have no field in the contract and are never read.
Default policies: drafts and Teams posts need an Approver, with at most 100 per run.
Contracts to draft DocuSign envelopes
Reads Dynamics 365 Sales opportunities at or above your close probability (80% by default), or files in a SharePoint "ready for signature" folder, every hour.
Safeguards: envelopes are always created as drafts and nothing is e-mailed. Sending is a separate governed action that legal approves. Envelopes are never voided, deleted or edited, and the opportunity is left unchanged.
Default policies: every DocuSign write needs a Compliance reviewer, with at most 25 drafts per run and one envelope per send approval.
Setup notes: legal adds the customer signer while reviewing each draft. SharePoint drafts link the document, and legal attaches the final version in DocuSign before sending.
Commerce low stock to purchase requests
Checks Magento or VTEX stock every hour and proposes a Xero draft purchase order, a Business Central purchase order or a Jira ticket for each product at or below the reorder point (10 by default). Alternatively, take Shopify or Adobe Commerce orders as provider-signed webhooks and propose one request per ordered line for the quantity sold.
Safeguards: purchase orders are proposals for approval, never sent, e-mailed or paid automatically. Prices, orders, customers, products and stock in the commerce system are never changed by the template.
Default policies: purchase requests need an Approver, with at most 50 per run, and quantities above 500 are refused.
Setup notes: a Business Central order is two chained steps, header then line, each with its own approval. Once the header is approved and written, the line's approval is requested automatically (see Two-step chained actions).
Qualified leads to accounting customers
Reads HubSpot contacts at lifecycle stage salesqualifiedlead, or qualified Dynamics 365 Sales leads, every hour.
Safeguards: read-only in your CRM. Creates customer records only, never invoices, quotes, payments or credit terms. Duplicates are never merged.
Default policies: customers.upsert (QuickBooks) or contacts.create (Xero) need an Approver, with at most 100 per run.
Setup notes: approvers see the qualification rule next to the proposed customer fields. QuickBooks matches customers by display name, so keep names consistent between systems.
Install a template
Connect the systems the template uses and test each connection.
Switch on the write operations the template needs on each connection, for example invoices.create on QuickBooks Online.
Open the template, choose Install template, then pick the project, any options (for example the CRM or delivery channel) and your connections.
Review Policies on your connections. Policies for connections you have not chosen are listed as pending and apply as soon as you bind them.
Fill in the placeholders the setup notes name (supplier IDs, template IDs, match tables), run the suggested checks, then publish.
Over the API:
POST /api/console/connect/templates/commerce_order_to_procurement/install
Content-Type: application/json
{
"projectId": "<project id>",
"name": "Low stock to Xero",
"choices": { "commerce": "magento", "purchase_request": "xero_draft_po" },
"connections": {
"magento-open-source": "<connection id>",
"xero": "<connection id>"
}
}The response contains the integration, its draft flows and a governance block. Each applied policy reports its action: create (new policy), tighten (a weaker policy was replaced) or keep (your stricter policy was left as it is). Binding connections needs the connect.policy.manage permission. Read a template's choices, safeguards and setup notes with GET /api/console/connect/templates/:templateKey.
Next
Flow triggers and inputs: uploads, signed webhooks and chained steps.
Govern overview: change or extend the policies a template applied.