Draw the workflow. We’ll run it.
The document workflows you currently run by email - forms, reviews, generated PDFs, signed packages - drawn on a canvas and executed step by step.
Build
Draw the process on a canvas. Pick a form template and a PDF template per step.
Run
Send participant emails. Each person gets a tokenized link to the action they own.
Notify
Branded transactional emails. In-flow notifications, signer invites, final-document delivery.
Bundle + sign
Generated PDFs combine into one document. Multiple signers route through it in order.
Verify
PKCS#7 signature + AATL timestamp + audit-trail page. Confirms in Adobe Reader offline.
1 · Build
Start with a canvas.
Drop the steps you need into a diagram of the process: a form, a review, a generate step, a signing step. Pick the templates each step uses, the role that owns it, and the field mappings between forms and PDFs. Save it as a workflow you can launch any time.
Drag nodes, connect them, hit Auto-format.
Triggers, forms, reviews, document sources, role assignment, signing, document generation, packaging, audit trail - wire any combination. The layout solver sizes each column to its contents so edges don't slide under unrelated nodes.
- Manual or scheduled triggers
- Parallel branches that join automatically
- Undo / redo and per-edit autosave
One master template. Different text per client.
Define a group of named text snippets - say, five fee schedules or three custodians. The template has a labeled placeholder where one of them belongs. When you launch the workflow, pick which snippet to drop in. Same template across every tier; the right text lands in the right document.
- Snippets live in groups: Fee Schedule, Custodian, Risk Disclosure
- Each group holds named options with bold / italic / currency formatting
- Pick the option for this client when launching the workflow
2 · Run
Launch it. The engine works through every step.
When the engine reaches a step that needs a person, the assigned participant gets a tokenized link to that one action - no account, no login. Automatic steps (generate, package, audit) run on their own. Reviews can approve, reject, or send a flow back.
Clients open a link, fill the form, submit.
Text, email, phone, address, currency, date, dropdown, multi-select, file upload, and more - each rendered consistently and validated before submission. Drafts persist per-keystroke so a closed tab isn't a lost session.
- Tokenized signer link - no account required
- Per-keystroke autosave
- Required-field and conditional rules
Every running flow on one page.
Each row shows the workflow's current step, the named participant blocking it, and what they owe. Automatic steps (generate, package, audit) run on the engine; manual steps wait for the right person.
- Blocking participant inline on every row
- Per-event log: viewed, edited, signed - with actor, IP, and timestamp
- One-click retry for failed automatic steps
- Search by client, workflow, or signer email
3 · Notify
People hear from you, not from us.
Every step that needs a person triggers a branded email — signer invites, in-flow notifications, the signed-copy delivery when the workflow finishes. The author writes the subject and body in the editor; the engine fills in form data with{{form.fieldKey}}substitution and renders the same branded shell across every message.
What signers actually see.
Sent the moment a step becomes that person’s turn. The deep link is tokenized to one action, the expiry is shown inline, and the disclaimer + footer follow standard transactional-email hygiene so nothing trips spam filters.
- One-click button + plain-text fallback URL collapsed under a disclosure
- Tokenized link expires automatically — no account, no login
- “Didn’t expect this email?” disclaimer + support contact
- Inline brand mark renders in Gmail web, Apple Mail, modern Outlook
KYC Onboarding — Pinegrove Capital
Hi Jordan,
You have a sign document step waiting for you in RapidSign. Open the document below to continue.
Trouble with the button? Use this link instead
https://rapidsign.ca/workflow/8af6a7c1/sign/8e786a53#token=050de10f1f1d63
Participant invites
Fill-form, sign-document, and review steps fire an invite the moment they activate. Idempotent — re-running the engine doesn't double-send.
In-flow send_email steps
Drop an Email node into the canvas to send anywhere mid-workflow. Subject and body support {{form.fieldKey}} substitution against any collected form data.
Final-document delivery
Audit-trail step optionally emails the signed PDF to a configurable recipient list — including resolving an address from a form field.
4 · Bundle + sign
Multiple PDFs become one signed document.
Once forms are submitted, the generate step fills the PDF template with the captured fields. A package step concatenates the generated documents - KYC, LRD, cover sheets, any static attachments - into a single PDF. The signing step routes that bundle to each signer with handles placed where they need to sign.
Combine documents before signing.
A package node concatenates multiple PDFs into one document while preserving field positions across the merged pages. The next signing step places handles anywhere in the combined bundle.
- Generated PDFs + static attachments in one file
- Field positions preserved through the merge
- Signing handles can land on any merged page
Multiple signers, in sequence or in parallel.
When the signing step runs, each signer gets a tokenized link to the bundle. They open it in the browser and sign the fields routed to them by role. The next signer is unblocked automatically when the previous one finishes; parallel signers can act at the same time.
- Sequential or parallel signer ordering
- Role-based routing defined once in the builder
- Signers reach the document without logging in
Open the file. Adobe confirms it.
Every completed signing step embeds a standard PKCS#7 digital signature directly into the PDF, timestamped by an Adobe-trusted (AATL) third-party authority. The audit trail - every viewed, edited, and signed event with actor, IP, and timestamp - is rendered as a final certificate page and appended to the bundle. Open the file in Adobe, Foxit, or Preview: the reader confirms the document hasn’t been altered since the last signature, with the audit page right there in the PDF.
- Cryptographic hash of the document captured at sign-time
- One PKCS#7 signature per signer, in signature order
- Trusted timestamp from GlobalSign, SwissSign, Sectigo, or Entrust (AATL)
- Audit-trail certificate page appended to every final PDF
- “Verified” status visible inline on every signed PDF
Any byte changed in the document after signing invalidates the signature - so a tampered file is immediately detectable.
- Signed by
- Jordan Reed
- Algorithm
- SHA256withRSA
- Certificate
- CN=Jordan Reed, O=Pinegrove Capital
- Issued by
- GlobalSign AATL CA · GlobalSign
- TSA
- May 26, 2026, 12:00:09 AM
- GlobalSign Timestamping CA
- Valid
- Jan 1, 2026 to Dec 31, 2027
Every signed bundle ends with this certificate.
The workflow name, instance ID, every participant, every step with its started and completed timestamps, every signer, and the full event log with IP and timestamp on each row. Rendered straight from the audit log when the workflow completes - nothing hand-curated.
- Document Summary - workflow, instance ID, who started it, when
- Workflow Steps - each step with started + completed timestamps and the signers who acted
- Detailed Audit Log - every viewed, edited, and signed event with actor and IP
- Sits inside the signed PDF - included in the PKCS#7 hash, so tampering is detectable
6 · Organize
Every signed bundle ends up on the client’s profile.
After the workflow finishes, the signed document is filed against the client whose data it carries. Pull up that client and every form they’ve submitted and every PDF they’ve signed is right there - grouped by the template that produced it.
One profile per client, every document filed under it.
Every submission and signed package across every workflow gets attached to the same profile, grouped by the template that produced it. Open a profile and inline-preview any signed PDF without a download.
- Per-template tabs that group related submissions
- Inline previews - no downloads required
- Export CSV or JSON in one click
Group clients by household, advisor, or any captured field.
Define views that aggregate profiles by any field you collect. Filter, search, and bulk-launch workflows across many clients at once.
- Multiple views per team
- Bulk-select to launch workflows across many clients
- XLSX export of any view's columns
Security
Every action logged. Every link scoped. Every signed PDF verifies on its own.
Tenant isolation
Company data separated at the database level - cross-tenant queries impossible by design.
Tokenized signer links
Each link unlocks exactly one action for one signer. No account, no login required.
Per-event log
Viewed, edited, signed - actor, IP, and timestamp recorded on every event.
Reliable webhooks
Retried on failure with a dead-letter queue for anything that ultimately fails.
See it on your process.
Show us a workflow you currently run by email. We’ll rebuild it for you.
Request a demo