--- title: "Adobe Acrobat Sign Integration" description: "Send documents for e-signature with Adobe Acrobat Sign. Agents upload files, send and track agreements, chase signers with reminders, pull completed form data, and download signed PDFs and audit trails." url: https://flowrunner.ai/integrations/adobe-sign date_modified: 2026-08-01T02:40:32-07:00 --- # Adobe Acrobat Sign [Documents](https://flowrunner.ai/integrations/category/documents-forms) Send documents for e-signature with Adobe Acrobat Sign. Agents upload files, send and track agreements, chase signers with reminders, pull completed form data, and download signed PDFs and audit trails. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 21 actions · OAuth · available [Adobe Acrobat Sign website](https://www.adobe.com/acrobat/business/sign.html) · [Platform Documentation](https://opensource.adobe.com/acrobat-sign/developer_guide/) · Capability data verified 2026-08-12 1. A deal closes in the CRM and the contract needs to go out for signature 2. Upload Transient Document stages the generated contract PDF in Acrobat Sign 3. The deal owner reviews the recipients and terms before anything reaches the counterparty 4. Send Agreement sends the approved contract, each recipient signing in order 5. Get Agreement polls status until the agreement reports SIGNED, with Send Reminder nudging slow signers along the way 6. Download Agreement PDF and Download Audit Trail archive the executed contract and its certified record 7. The flow posts completion to the deal channel with links to the archived documents ## What This Integration Enables An e-signature is a moment, and everything around that moment is logistics: preparing the document, sending it, chasing it, retrieving it, filing it, extracting what the signer typed into it. Acrobat Sign owns the moment. FlowRunner agents own the logistics. The connector covers the full agreement lifecycle, from Upload Transient Document through Send Agreement to Download Audit Trail, so the only human touches left are the ones that should be human: deciding what goes out, and signing. - Send contracts, NDAs, and offer letters for signature and follow them to completion - Start from reusable library templates instead of fresh uploads each time - Embed signing links in your own email or app with Get Signing URLs - Nudge specific slow signers with targeted reminders - Archive signed PDFs and certified audit trails into FlowRunner file storage for compliance - Pull signer-entered field values out of completed agreements as structured data The send itself stays gated. FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) orchestration means the agent assembles everything and a person clears the moment a contract leaves the building. ### Without FlowRunner **Contracts stall in outboxes**: The deal is done but the paperwork waits for someone to assemble, attach, and send **Chasing signers by hand**: Somebody keeps a mental list of who has not signed and writes the awkward nudge emails **Signed PDFs scattered**: Executed contracts live in whoever's inbox received them, and the audit trail never gets saved at all ### With FlowRunner **Signature starts when the deal does**: The contract is staged, approved, and out for signature minutes after the trigger fires **Reminders on a schedule**: Agents track status and remind exactly the participants who have not acted, with a note **Every contract lands in the archive**: The combined PDF and the certified audit trail file themselves, every time, before anyone asks ## Use Case Scenarios ### Closed-won to out-for-signature in one motion A deal moves to closed-won in [HubSpot](https://flowrunner.ai/integrations/hubspot). The agent pulls the contact, stages the contract with Upload Transient Document, and posts the recipient list and key terms to the deal owner. On approval, Send Agreement fires. From there the agent polls Get Agreement, and when status hits SIGNED, it downloads the executed PDF, updates the CRM, and posts the close to [Slack](https://flowrunner.ai/integrations/slack). The rep never opens Acrobat Sign. ### The compliance archive that builds itself A scheduled sweep calls List Agreements and checks each recently completed agreement with Get Agreement. For every newly SIGNED agreement, the agent calls Download Agreement PDF with the audit report appended, calls Download Audit Trail for the standalone certified record, and files both into a structured folder in [Google Drive](https://flowrunner.ai/integrations/google-drive-api). Get Form Data extracts the signer-entered fields, names, dates, custom terms, into a tracking row in [Google Sheets](https://flowrunner.ai/integrations/google-sheets). When an auditor asks for the paper trail, it is already a folder, not a scavenger hunt. ### The reminder that names the right person Three days after sending, an agreement still reads OUT\_FOR\_SIGNATURE. The agent calls Get Agreement Members to find exactly which participant has not acted, then Send Reminder targeted to that participant ID with a courteous note. Two days later, if nothing moves, the agent escalates to the deal owner with the full event history from Get Agreement Events: who viewed, who signed, who went silent. The owner decides whether to call, resend, or cancel. Nobody reminds someone who already signed. ## Human-in-Loop Highlight Send Agreement is the operation that reaches a counterparty with binding intent. The moment it fires, a real person at another company receives a contract from your name, and every recipient becomes a participant in a legally significant process. Send the wrong version, the wrong terms, or the wrong recipient list and the recovery is Cancel Agreement plus an apology that lives forever in the relationship. So FlowRunner agents stage aggressively and send reluctantly: Upload Transient Document and Create Draft Agreement do the assembly at machine speed, and the flow pauses with the document, recipients, and signing order in front of the deal owner. One approval, then Send Agreement fires. The automation saves the hour of assembly; the human spends ten seconds preventing the one send that could not be unsent. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 21 actions ### Documents and Sending 3 - **Upload Transient Document** Uploads a FlowRunner file to Acrobat Sign as temporary staging (kept about 7 days) and returns the transientDocumentId used by Send Agreement or Create Draft Agreement. Supports PDF, Word, Excel, PowerPoint, text, and common image types. - **Send Agreement** Creates an agreement and immediately sends it for signature from a transient document or library template, each recipient signing in the listed order. The send this page's human gate exists for. - **Create Draft Agreement** Creates an agreement in DRAFT state without sending, so it can be reviewed or completed in the Acrobat Sign web app first. Same inputs as Send Agreement. ### Tracking and Follow-Up 7 - **List Agreements** Lists the connected user's agreements, most recent first, with ID, name, and status. The sweep behind archive and follow-up workflows. - **Get Agreement** Retrieves a single agreement in full: status, participant sets, sender, expiration, and message. The polling step that tells a flow when signing completes. - **Cancel Agreement** Cancels an in-process agreement so it can no longer be signed, optionally notifying remaining participants. The recovery step when terms change mid-flight. - **Get Signing URLs** Retrieves the current signers' signing links, for embedding in your own email or app. Only available while the agreement is out for signature. - **Get Agreement Members** Lists every participant with ID, email, role, order, and status. The lookup that tells a reminder exactly who has not acted. - **Get Agreement Events** Retrieves the audit event history: sent, viewed, signed, delegated, reminded, cancelled, completed, each timestamped. The timeline behind escalation decisions. - **Send Reminder** Sends a reminder email to specific participants who have not yet acted, with an optional note. Targeted nudging instead of blanket resends. ### Retrieval and Data 4 - **Get Form Data** Retrieves signer-entered form field data as CSV, parsed into row objects when possible. The extraction step that turns a signed agreement into structured data. - **Download Agreement PDF** Downloads the combined agreement PDF into FlowRunner file storage, optionally with supporting documents and the audit report appended. The archive step. - **Download Audit Trail** Downloads the certified audit trail PDF, who did what and when, into FlowRunner file storage. Commonly filed alongside the signed document for compliance. - **List Agreement Documents** Lists the individual documents inside an agreement with ID, name, MIME type, and page count. ### Templates and Web Forms 4 - **List Library Documents** Lists the reusable library templates available to the connected user. The starting point for template-driven sends. - **Get Library Document** Retrieves a single template's details: name, status, sharing mode, and template types. - **List Web Forms** Lists the connected user's hosted signing forms with ID, name, status, and URL. - **Get Web Form** Retrieves a single web form's hosted URL, embed code, and creation info, for sharing or embedding. ### Account 3 - **Get Current User** Retrieves the connected user's profile: ID, email, company, account and group membership. The connection check. - **List Users** Lists users in the account with ID, email, name, and company. Requires an account administrator connection. - **List Groups** Lists the account's visible groups with ID, name, and creation date. Groups organize users and templates. ## Frequently Asked Questions ### What can FlowRunner do with Adobe Acrobat Sign? FlowRunner agents can run Upload Transient Document, Send Agreement, and Create Draft Agreement in Adobe Acrobat Sign, plus 18 more actions. ### Does connecting Adobe Acrobat Sign to FlowRunner require OAuth? Yes. Adobe Acrobat Sign connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Adobe Acrobat Sign trigger a FlowRunner workflow automatically? Adobe Acrobat Sign doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Adobe Acrobat Sign?** This integration exposes Adobe Acrobat Sign to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/adobe-sign. Site index: https://flowrunner.ai/llms.txt