
Connectors / Sales · HTTP Connector
Automate GetAccept with Tray.ai
Create a document, create a contact and create a product in GetAccept, and start a workflow when GetAccept sends “Document created”.
Thanks — someone from our team will be in touch soon.
What can you do with GetAccept on Tray.ai?
GetAccept is a sales document platform where teams send proposals and contracts for e-signature, track how buyers engage with them, and share deal rooms. Tray.ai connects to GetAccept through the HTTP Connector, so your workflows can call the GetAccept API alongside the rest of your stack. API access comes through GetAccept's partner program or API plan, so you need approved credentials first.
- When GetAccept sends “Document signed”, mark the deal closed won in your CRM.
- When GetAccept sends “Document viewed”, alert the account owner in your team chat so they can follow up.
- Create a document from a template when a deal reaches the proposal stage in your CRM.
- When GetAccept sends “Document expired”, open a follow-up task for the sales rep.
- Connects through
- HTTP Connector
- Authentication
- OAuth 2.0 or a bearer token
- Base URL
- https://api.getaccept.com
Set it up
Connect GetAccept to Tray.ai
Each step uses GetAccept's own API details, from its documentation.
Step 1
Sign in to GetAccept with OAuth 2.0
Ask GetAccept for API access. Once it's approved, set up an OAuth 2.0 authentication with the client ID and secret of an OAuth app you register with GetAccept. Sign in once and every step reads the token from there.
Step 2
Point the HTTP Client at the API
Add an HTTP Client step and use https://api.getaccept.com as the base URL. Or paste a cURL example from GetAccept's API docs, and Tray.ai fills in the method, URL, and headers.
Step 3
Start with “List documents”
It's one of 23 documented actions, under Documents. The response comes back as data the next step can map into your other apps.
Step 4
Start workflows from GetAccept events
Give GetAccept the URL of a Tray.ai webhook trigger. “Document created” can then start a workflow, and so can 8 other events.
What the GetAccept API covers
6 resources and 23 documented actions, each one a call the HTTP Connector can make from a Tray.ai workflow. GetAccept gives API access on request, so approved credentials come first. Connecting it takes a few clicks: here's how.
Documents
- List documents
- Create a document
- Get a document
- Send a document
- Download a document
- Recall or delete a document
Templates
- List templates
- Get a template
- Get template fields
Contacts
- List contacts
- Create a contact
- Delete a contact
Users
- List users
- Create a user
- Get a user
- Delete a user
Products
- List products
- Create a product
- Update a product
- Delete a product
Event subscriptions
- List subscriptions
- Create a subscription
- Delete a subscription
Events GetAccept can send to a Tray.ai webhook trigger
- Document created
- Document sent
- Document viewed
- Document signed
- Document partially signed
- Document rejected
- Document expired
- Document recalled
- Document commented
Checked against GetAccept's own documentation on 2026-10-22
How Tray.ai makes this work
GetAccept plugs into the whole Tray.ai platform
Intelligent Integration
Integrate and automate across 9,000+ apps, databases, APIs, and services with visual workflows, error handling, and observability.
Learn more →Agent Builder
Build AI agents that read, write, and take action in GetAccept — with guardrails, audit, and human-in-the-loop.
Learn more →Agent Gateway for MCP
Expose GetAccept actions as governed MCP tools — observable, rate-limited, authenticated.
Learn more →Tray Helix
Build apps on GetAccept data with your AI assistant, then deploy, run, and govern them on Tray.ai.
Learn more →More sales apps on Tray.ai
Dedicated connectors and other apps Tray.ai reaches in the same category. See every sales connector →
Frequently asked questions
What can a Tray.ai workflow do in GetAccept?
+
The GetAccept API documents 23 actions across 6 resources (Documents, Templates, Contacts, Users, Products, Event subscriptions). For example: List documents; List templates; List contacts. A workflow can make any documented call through the HTTP Connector.
How does Tray.ai authenticate with GetAccept?
+
The GetAccept API uses OAuth 2.0 and a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.
Which GetAccept events can start a Tray.ai workflow?
+
GetAccept sends 9 events to a webhook URL, for example: Document created; Document sent; Document viewed; Document signed; Document partially signed; Document rejected; Document expired; Document recalled. A Tray.ai webhook trigger receives them and starts a workflow.
Do I need special access to the GetAccept API?
+
Yes. GetAccept gives API access on request, so you need approved credentials before a Tray.ai workflow can call it.
See GetAccept working against your stack.
We'll walk through a tailored demo with your systems plugged in.
Thanks — someone from our team will be in touch soon.