We’re about to roll out a bulk signature process for 300 subcontractor certificates across a 60‑house residential prog…
Log in to your Adobe Acrobat Sign admin console with an account that has integration permissions.
Navigate to Account Settings and select Workflow Integration.
Enable Power Automate Workflows by selecting the corresponding option.
CautionYou must enable this setting before you can use Power Automate or Zapier to trigger bulk send actions.
In your integration platform (e.g., Power Automate or Zapier), create a new workflow or zap.
Add an action to connect to Adobe Acrobat Sign using the official connector or app.
Configure the action to use the Send in Bulk (SiB) feature, specifying your parent template and recipient list as required.
Best practiceFor best deliverability, send small batches (e.g., 10 emails per hour) to avoid domain reputation issues.
Map any dynamic fields or data sources from your workflow to the corresponding fields in the bulk send template.
Test the workflow with a small recipient list to ensure agreements are sent and tracked correctly.
Best practiceAvoid sending PDF attachments directly; use document links to reduce spam risk and improve analytics.
Activate or schedule the workflow to trigger bulk send actions as part of your automated business process.
You can monitor the status of each bulk agreement sent via integration from the Acrobat Sign Manage page.
The Adobe Acrobat Sign API supports bulk send via the POST /agreements endpoint with a recipient list payload.
The Bulk Send feature in Adobe Acrobat is for sending a single document to many different people for their individual signatures. It is designed for situations where you need to collect many unique signatures on the same form, ensuring each signer receives a private copy and has their own audit trail. This saves time compared to sending documents one by one.
No, when you use Bulk Send, each signer receives their own independent 'child agreement'. This means signers do not see each other's names or email addresses. Each agreement is private and has its own separate audit trail, ensuring confidentiality and individual tracking for every signature request.
Bulk Send counts against transaction limits because each 'child agreement' created from the parent template is considered a separate, distinct transaction. Even though you start with one document, sending it to 500 people creates 500 individual agreements, each requiring processing, tracking, and an audit trail. This makes it important to monitor your transaction limits when using Bulk Send for large volumes.
| Feature | Recipients See Each Other | Number of Agreements | Best Use Case |
|---|---|---|---|
| Normal Multi-Recipient Send | Yes (often in CC/BCC) | One (with multiple signers) | Collaborative signing, sequential workflow |
| Bulk Send | No (each is private) | Many (up to 1,000) | Mass distribution for individual signatures |