Integration
Connect Rendobar to SigningHub
When Job completed fires in Rendobar, 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 Rendobar 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 Rendobar can start in SigningHub
When Job completed in Rendobar
then Add Document 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 Rendobar and SigningHub
Triggers and actions 1 trigger · 23 actions
- Job completed
Fires when a job finishes (success/failure). Backed by the vendor's webhook endpoint delivery mechanism, filtered to job-completion events.
- Add asset
Initialize an asset (media file) upload.
- Add job
Create a media processing job (transcode, caption, watermark, etc).
- Cancel job
Cancel a running job.
- Delete asset
Delete an asset by id.
- Get asset
Get details of an asset by id.
- Get job
Get details of a job by id.
- Get job logs
Get execution logs for a job.
- Get job output
Get the download URL/content for a completed job's output.
- List assets
List uploaded assets.
- List jobs
List jobs for the account.
- List job types
List available job types (transcode, caption, watermark, etc).
- List models
List available generation/processing models.
- Add Digital Signature
Adds a digital signature field to a document in a SigningHub package and assigns it to a recipient in the workflow.
- Add Document
Uploads a document file into an existing SigningHub document package.
- Add Electronic Signature
Adds an electronic signature field to a document in a package, assigned to a recipient in the workflow.
- Add Recipient to Workflow
Adds a signer or other recipient to a document package's workflow.
- Add User
Registers a new user in your SigningHub enterprise account, optionally with a password, role and profile details.
- Create Integration URL
Generates an encrypted SigningHub link that opens a shared document package so a user can view and sign it from your application.
- Create Package
Creates a new document package in SigningHub to hold documents and recipients for a signing workflow.
- Download Package
Downloads a document package as a Base64-encoded file: a PDF for a single-document package, or a zip of all its documents.
- Get Document Fields
Returns the fields on a document in a SigningHub package: signature, initials, in-person, text, checkbox, radio, dropdown, listbox, QR code, attachment and comment fields.
- Get Package
Returns the details of a SigningHub document package: its name, owner, status and the documents it contains.
- Share Document for Signing
Shares 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 Rendobar
Rendobar to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Rendobar to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Rendobar to StripeStripe is a payment processing platform for online businesses.
Rendobar to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Rendobar to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Rendobar to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into SigningHub
HubSpot to SigningHubHubSpot is your all-in-one stop for all of your marketing software needs.
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
Rendobar and SigningHub, answered
What can start an automation from Rendobar?
Any of Rendobar's 1 trigger in the catalog, including Job completed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SigningHub when something happens in Rendobar?
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 Rendobar?
SigningHub has no triggers in the catalog today, so automations start in Rendobar. 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 Rendobar 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 Rendobar 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.