A workflow puts several templates behind one form. Your customer answers once, the rules decide which documents belong, every document fills from the same answers, and one signature fills every signature line.

Can a document join only when a rule is true?

Yes. Each document can carry a rule, such as an additional insured, a state, or a limit above a threshold. When the rule is false the document is skipped, so the packet only holds what applies.

How does the packet come back?

As one merged PDF, as separate files, or both, set per workflow. Each run can also produce a certificate of completion: its own PDF, with the signing details captured for that run, the times and a SHA-256 of the documents.

workflows

A whole packet. From one form.

Put your fillable PDFs and smart documents behind one form. Your customer answers once, rules decide which documents belong, and every page fills from the same answers.

Start free See the API

1Answers
One form, filled once, by your customer or your code.
2Rules
Each document can carry a rule. When it is false, the document is skipped.
3Documents
Fillable PDFs and smart documents fill from the same answers.
4Packet
Merged, separate or both, plus a certificate of completion as its own PDF.
5Webhook
Your server hears when the run completes or fails.

Watch a packet build itself.

Answer as the broker would. Documents join or drop out by rule, the same way your real packets do with the rules your team sets.

The broker's answers

How the packet comes back

Binder packet, Harbor Point LLC6 of 8 documents

01ACORD 125 applicationAlways in
02Quote letterAlways in
03BinderAlways in
04ACORD 25 certificateAlways in
05Additional insured endorsementadded by rule: additional_insured = trueBy rule
06Hurricane deductible noticeSkipped
07Surplus lines noticeadded by rule: placement = surplus linesBy rule
08Premium finance agreementSkipped

One merged PDF. The certificate of completion comes as its own file.

Rules decide what is in the packet.

Three risks, one workflow. Documents without a rule are always in. The rest join only when their rule is true.

Documents in the packet for three sample cases
Document	Texas, retail	Florida, additional insured	Surplus lines, financed
Applicationalways in	Included	Included	Included
Quote letteralways in	Included	Included	Included
Binderalways in	Included	Included	Included
Certificate of insurancealways in	Included	Included	Included
Additional insured endorsementrule: additional_insured	Skipped	Included	Skipped
Hurricane deductible noticerule: state = FL	Skipped	Included	Skipped
Surplus lines noticerule: placement = surplus	Skipped	Skipped	Included
Premium finance agreementrule: premium_financed	Skipped	Skipped	Included

Explore insurance policy packet automation for US MGAs

What comes back.

Pick the output per workflow. A run counts as one document on your plan, however many files it produces.

One merged PDFEvery included document, in order, as one file.
Separate filesEach document as its own PDF, named by its alias.
BothThe merged packet and the separate files together. Download one document, the merged PDF, or a zip of everything.

Certificate of completion

Its own PDF

On by default, for every run. It records:

Organization: Your company, as set in Mezdoc
Workflow: Its name and the published version
Run: The run ID and the environment
Documents: How many, and the total page count
Fingerprint: A SHA-256 of the delivered documents
Signer: Email when a code was used, IP address and device
Times: When the run started and completed

Versions that never surprise a renewal.

Every publish is a snapshot and every run records the template versions it used. Publish the next version when it is ready, and restore an earlier one when finance flags a typo.

One snapshot per publish
Restore any earlier version
Each run records the versions it used

Send one link, or make one call.

The same workflow runs from a hosted link or from your code.

A link you control

An email code before the form opens, on by default.
Expires after 7 days by default, or when you choose.
Stops after a set number of uses, if you want it to.
Can refuse to submit until every required signature is in.

Run a workflow

curl -X POST https://api.mezdoc.com/api/v1/workflows/renewal_packet/runs \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "data": { "insured_name": "Harbor Point LLC",
                "state": "FL" } }'

# 200 OK: run_id, merged_pdf_url, document_pdf_urls
# with ?async=true: 202, then the webhook
workflow.run.completed  workflow.run.failed

Questions about workflows.

What is a workflow?: A workflow puts several templates behind one form. Your customer answers once, the rules decide which documents belong, every document fills from the same answers, and one signature fills every signature line.
Can a document join only when a rule is true?: Yes. Each document can carry a rule, such as an additional insured, a state, or a limit above a threshold. When the rule is false the document is skipped, so the packet only holds what applies.
How does the packet come back?: As one merged PDF, as separate files, or both, set per workflow. Each run can also produce a certificate of completion: its own PDF, with the signing details captured for that run, the times and a SHA-256 of the documents.

From form fill to signed packet, in one go.

Build your first workflow from the documents you send today, add the rules, and send the link.

Start free Talk to us

Free plan, no card