GetAccept
DocumentsConnect AI agents to GetAccept, the digital sales room and e-signature platform. Agents create documents from files or templates, attach recipients, send them for signing, track status through the deal lifecycle, and keep contacts in sync with your CRM.
What This Integration Enables
GetAccept treats a contract as a deal room, not a PDF attachment: the document carries recipients, tracking, merge fields, and a lifecycle from draft to signed. That structure is what makes it automatable. FlowRunner agents create documents from files or templates, attach signers, approvers, and viewers with their proper roles, dispatch them for signature, and read status back as the deal progresses. Contacts and users are queryable, so recipient resolution happens against records instead of retyped email addresses. The division of labor is deliberate. Agents do the assembly: template selection, field merging, recipient lookup, status polling. People do the judgment: whether this contract, at this value, with these terms, is ready to reach this buyer. That handoff is FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) layer, and on this connector it sits exactly at the send. - Create documents from a file URL or base64 content, or from a stored template with merge fields - Attach recipients as signer, cc, approver, or viewer in the same call that creates the deal - Hold documents in draft for review, or set Send Immediately for low-stakes flows like NDAs - Poll document status and read back field values to drive downstream steps - Keep GetAccept contacts synced with the CRM so recipients are never invented at send time
Without FlowRunner
With FlowRunner
Use Case Scenarios
Contract-stage deals become sales rooms without rep assembly
A [HubSpot](/integrations/hubspot) deal hits the contract stage. The agent pulls the deal record, calls List Templates to select the right proposal template, resolves the buyer with List Contacts, and creates the missing contact if needed. Create Document merges deal value, terms, and legal names into a draft, and List Document Fields verifies nothing came through blank. The rep gets the draft link, approves, and Send Document dispatches it. The rep's contribution shrank to the one step that needed them: reading the contract.
Signature status drives the close process instead of trailing it
After dispatch, an agent polls Get Document on a schedule. When the status shows signed, the flow marks the deal closed-won in the CRM, logs deal name, value, and signer to [Google Sheets](/integrations/google-sheets) for revenue reporting, and posts the win to [Slack](/integrations/slack). When a document sits unopened past the SLA, the agent surfaces it to the rep with the tracking detail from the sales room. Rejected documents open a task with the rejection context attached. Nobody refreshes a dashboard, because the statuses arrive as events in the flow.
Routine NDAs flow untouched, real contracts wait for a person
A prospect books a technical deep-dive through [Calendly](/integrations/calendly). The agent creates the standard NDA from its template with Send Immediately, because a template NDA to a known contact is a low-stakes, fully reversible interaction. The same flow handles a six-figure services agreement differently: Create Document holds it in draft, the agent posts the summary with value and non-standard terms flagged, and the deal owner approves before Send Document fires. One workflow, two risk profiles, and the gate placed only where the stakes justify it.
Human-in-Loop Highlight
Send Document is the moment a contract leaves your control. Once it lands in the buyer's sales room, the pricing, the terms, and any mistake in them are in front of the customer, and no follow-up email fully unsends a wrong number on a legal document. Delete Document is the other edge: it permanently removes a deal and its sales-room content, and GetAccept may refuse it entirely for signed documents, which tells you how final it is. So FlowRunner agents assemble and verify at machine speed, but a named deal owner approves dispatch on anything above template-grade paper, and deletion of any document with signing history requires explicit human confirmation with the document's status in front of them. The agent's job is to make that approval a ten-second read, not to make it disappear.
Agent Capabilities
11 actionsDocuments
6- List Documents Lists documents (deals) in the connected GetAccept entity. Supports filtering by lifecycle status and free-text search, plus pagination. Use this to find a document ID for Get Document, Send Document, or Delete Document.
- Get Document Retrieves the full detail of a single GetAccept document by its ID, including status, value, recipients, and tracking metadata for the digital sales room.
- Create Document Creates a new GetAccept document (deal) from a file URL or base64 content and attaches its recipients. The document is created in draft by default; set Send Immediately to route it into the digital sales room and dispatch it for signing in one step. Recipient roles map to GetAccept's signer, cc, approver, and viewer.
- Send Document Sends an existing draft GetAccept document to its recipients for signing, moving it out of draft into the active sales-room flow. The document must already have recipients attached (via Create Document). Use this when you created a document in draft and want to dispatch it later.
- Delete Document Permanently deletes a GetAccept document by ID. This removes the deal and its associated sales-room content and cannot be undone. Documents that have already been signed may be restricted from deletion by GetAccept.
- List Document Fields Returns the merge/input fields defined on a GetAccept document, including field IDs, labels, types, and current values. Use this to discover what data can be prefilled or read back from a document or template-based deal.
Templates
1- List Templates Lists the document templates available in the connected GetAccept entity. Templates provide reusable content and field layouts for creating new documents. Returns template IDs and names for use when building deals.
Contacts
2- List Contacts Lists contacts stored in the connected GetAccept entity, with optional free-text search and pagination. Use this to look up an existing recipient before creating a document.
- Create Contact Creates a new contact in the connected GetAccept entity. Contacts can later be used as document recipients. Email is required; company, phone, and title enrich the contact record.
Account
2- List Users Lists the users (team members) in the connected GetAccept entity, returning their IDs, names, emails, and roles. Use this to identify who can own or be assigned to documents.
- Get Entity Retrieves account (entity) information for the connected GetAccept team, including entity ID, name, and configuration. Use this to confirm which account the credentials resolve to.
Frequently Asked Questions
What can FlowRunner do with GetAccept?
FlowRunner agents can run List Documents, Get Document, and Create Document in GetAccept, plus 8 more actions.
Does connecting GetAccept to FlowRunner require OAuth?
No. GetAccept connects to FlowRunner with session-based authentication, no OAuth flow required.
Can GetAccept trigger a FlowRunner workflow automatically?
GetAccept doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with GetAccept
$100 in credits. No card required. Connect in minutes.