Integration
Connect Trengo to SigningHub
When New Internal Note fires in Trengo, your agent runs Add Document in SigningHub. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Trengo and SigningHub to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Trengo can start in SigningHub
When New Internal Note in Trengo
then Add Document in SigningHub
When New Outbound Message in Trengo
then Add User in SigningHub
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Trengo and SigningHub
Triggers and actions 3 triggers · 26 actions
Trigger
New Internal NoteFires when an internal note is added to a Trengo ticket.
Trigger
New Outbound MessageTriggers when an outbound message is created.
Trigger
Ticket Label AddedTriggers when a label is added to a conversation.
Action
Add internal note to ticketAdds an internal note (visible only to agents) to a Trengo ticket.
Action
Add ticketCreate a new support ticket.
Action
Add ticket labelAttaches an existing label to a Trengo ticket.
Action
Create a ContactCreates a contact on a Trengo channel. If a contact with the same identifier already exists on that channel, Trengo returns the existing contact instead of creating a duplicate.
Action
Create webhookSubscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation.
Action
Delete contactDelete a contact by id.
Action
Delete ticketDelete a ticket by id.
Action
Find a ContactReturns the Trengo contacts that match the search term.
Action
Get contactRetrieve a single Trengo contact by its id.
Action
Get webhookFetches a webhook by ID, including the event it listens for, the address it sends to and its signing secret. An error occurs if the webhook is not found.
Action
List contactsList all contacts.
Action
List labelsLists the ticket labels defined in the Trengo account (first page).
Action
List ticketsReturns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time.
Action
Send a MessageSends a reply message on an existing Trengo ticket, over the ticket's own channel.
Action
Update contactUpdate an existing contact by id.
Action
Add Digital SignatureAdds a digital signature field to a document in a SigningHub package and assigns it to a recipient in the workflow.
Action
Add DocumentUploads a document file into an existing SigningHub document package.
Action
Add Electronic SignatureAdds an electronic signature field to a document in a package, assigned to a recipient in the workflow.
Action
Add Recipient to WorkflowAdds a signer or other recipient to a document package's workflow.
Action
Add UserRegisters a new user in your SigningHub enterprise account, optionally with a password, role and profile details.
Action
Create Integration URLGenerates an encrypted SigningHub link that opens a shared document package so a user can view and sign it from your application.
Action
Create PackageCreates a new document package in SigningHub to hold documents and recipients for a signing workflow.
Action
Download PackageDownloads a document package as a Base64-encoded file: a PDF for a single-document package, or a zip of all its documents.
Action
Get Document FieldsReturns the fields on a document in a SigningHub package: signature, initials, in-person, text, checkbox, radio, dropdown, listbox, QR code, attachment and comment fields.
Action
Get PackageReturns the details of a SigningHub document package: its name, owner, status and the documents it contains.
Action
Share Document for SigningShares a prepared document package with its signers and starts the signing workflow.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Trengo
Trengo to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Trengo to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Trengo to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
Trengo to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Trengo to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
Trengo to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
More into SigningHub
HubSpot to SigningHubHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SigningHubSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SigningHubSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SigningHubGoogle Sheets
Gmail to SigningHubGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SigningHubGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Trengo and SigningHub, answered
What can start an automation from Trengo?
Any of Trengo's 3 triggers in the catalog, including New Internal Note, New Outbound Message and Ticket Label Added. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SigningHub when something happens in Trengo?
Any of SigningHub's 11 actions, including Create Integration URL, Create Package, Add Digital Signature and Add Document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SigningHub to Trengo?
SigningHub has no triggers in the catalog today, so automations start in Trengo. If you need the other direction, ask: your agent reads SigningHub's API documentation and adds it.
Do I have to build a connector for Trengo or SigningHub?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Trengo and SigningHub without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.