Skip to main content

What is Email Execution?

Email execution allows you to trigger a document execution by sending an email to a unique email address. The email subject, body, and any attachments will be used as input for the execution. This is useful when you want to integrate a document into an email-based workflow without writing any code or calling the API directly.

Enabling Email Execution

To enable email execution for a document, follow these steps:
  1. Open the document in the editor.
  2. Navigate to the Integration tab.
  3. Select the Email tab.
  4. Toggle the Email execution switch to enable it.
Once enabled, a unique execution email address will be generated for your document. email execution disabled
The execution email address acts as a secret credential. Anyone with the address can trigger executions on your document. Treat it like an API key and do not share it publicly.

Your Execution Email Address

After enabling email execution, you can view and copy your document’s execution email address from the Email tab of the Integration page. email execution enabled The email address is hidden by default. Click the eye icon to reveal it, then use the Copy button to copy it to your clipboard.

Sending an Email

To trigger an execution, send an email to your document’s execution email address. The following parts of the email are passed as input to the document:
  • Subject — the email subject line
  • Body — the plain text body of the email
  • Attachments — any files attached to the email

Targeting a Specific Version

By default, the live (published) version of the document will be executed. To execute a different version, add one of the following tags to the email subject line:
  • [draft] — Execute the current draft version
  • [<version-uuid>] — Execute a specific version by its UUID
For example, an email with the subject Process this report [draft] would execute the current draft version of the document.

Attachments

Email execution supports file attachments. Attachments are uploaded and passed to the document as part of the execution input.
The total size of all attachments must not exceed 25 MB. The email body (excluding attachments) must not exceed 100 KB.

Viewing Execution Results

Executions triggered via email appear in the document’s execution history alongside API-triggered executions. You can view the input, output, and status of each execution in the Executions tab. If an email fails validation (for example, if the document has no published version), a failed execution record will still appear in the history so you can diagnose the issue.

Regenerating the Email Address

If you need to replace your document’s execution email address, click the Regenerate Email Address button in the Email tab of the Integration page.
The old email address will stop working immediately. Any integrations using the old address will need to be updated with the new one.

Disabling Email Execution

To disable email execution, toggle the Email execution switch off. This will revoke the current email address and prevent any further email-triggered executions.
The current email address will stop working immediately. Any integrations using this address will no longer be able to trigger executions.

Requirements

The document must have a published version for email execution to work, unless you are targeting the draft version by adding [draft] in the subject.
Learn more about publishing and versioning in the Versions section.