ActionAdobe Acrobat SignUpdated September 2026

How do I create a signature agreement in Adobe Sign?

Short answer: You can create signature agreement in Adobe Acrobat Sign by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Adobe Acrobat Sign Create Signature Agreement action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Create Signature Agreement in Adobe Acrobat Sign — start free All 3 Adobe Acrobat Sign actions

Create Signature Agreement in Adobe Acrobat Sign — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Agreement Name name	string	Required	–
Transient Document ID transientDocumentId	string	Required	–
Signer Email signer_email	string	Required	The email address. Used as the recipient or identifier depending on context.
Message message	string	Optional	–
State state	options	Optional	–

Sample request

{
  "name": "{{trigger.name}}",
  "transientDocumentId": "{{trigger.transientDocumentId}}",
  "signer_email": "e.g. user@example.com",
  "message": "{{trigger.message}}",
  "state": "{{trigger.state}}"
}

Returns

{
  "id": "agr_abc"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Create Signature Agreement.

Any of these apps can fire this action as part of a workflow.

Gmail → Adobe Acrobat Sign

1 Gmail triggers

Slack → Adobe Acrobat Sign

13 Slack triggers

Google Sheets → Adobe Acrobat Sign

2 Google Sheets triggers

HubSpot → Adobe Acrobat Sign

18 HubSpot triggers

FAQ

Questions about Create Signature Agreement.

What does the Create Signature Agreement action do in Adobe Acrobat Sign?

Creates a new signature agreement from a previously uploaded transient document, with the configured signers and signing order. Adobe Sign sends the first signer the email immediately (or all signers in parallel for unordered). Pair with Upload Transient Document — the two-step is Adobe's recommended pattern for programmatic sending.

What inputs does Create Signature Agreement require?

Required: Agreement Name, Transient Document ID, Signer Email. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Adobe Acrobat Sign returns an error?

The run history shows the failed step with its input and the error message Adobe Acrobat Sign returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Create Signature Agreement support batch operations?

Run Create Signature Agreement inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Adobe Acrobat Sign's rate limits.

More actions

Other Adobe Acrobat Sign actions.

Action

Get Agreement Status

Returns the current state of an agreement — per-signer status (sent, viewed, signed, declined), audit trail, and download URLs for the signed PDF once all signers complete. Poll this for completion or pair with the agreement-completed webhook for push-based notification.

Action

Upload Transient Document

Uploads a PDF or Word document to Adobe Sign's transient storage — returns a document ID valid for 7 days. The first step in the create-agreement flow; decouples upload from agreement creation so the same document can drive multiple parallel agreements without re-uploading.

Create Signature Agreement in Adobe Acrobat Sign — start free