Integration
Connect Cal.com to Signatureapi
When something happens in Cal.com, your agent does the next thing in Signatureapi. Describe it 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 Cal.com and Signatureapi to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Cal.com can start in Signatureapi
When Booking Created in Cal.com
then Add ceremony in Signatureapi
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 Cal.com and Signatureapi
Triggers and actions 5 triggers · 15 actions
- Booking Cancelled
Triggers when a booking is cancelled.
- Booking Created
Triggers when a new booking is created.
- Booking Rescheduled
Triggers when a booking is rescheduled.
- Meeting Ended
Triggers after meeting ends.
- Out of Office Created
Triggers when a new Out Of Office entry is created.
- Add ceremony
Creates a new signing ceremony for a recipient. Any previous active ceremony for that recipient is revoked. Returns the ceremony, including its URL when the recipient is authenticated by email code or by your own application.
- Add deliverable
Creates an additional deliverable (signed PDF package) from a completed envelope. The envelope must be completed.
- Add envelope
Creates an envelope with documents and recipients and starts the signing process.
- Add upload
Uploads a PDF, DOCX or PNG file to SignatureAPI and returns a URL you can use as a document source when creating an envelope. Uploads expire after 24 hours.
- Cancel envelope
Cancel an in-progress envelope so remaining recipients can no longer sign.
- Delete envelope
Delete an envelope.
- Get deliverable
Retrieves a deliverable by its ID, including its status and, once generated, a download link for the signed PDF.
- Get envelope
Retrieve a single envelope by id.
- Get recipient
Retrieves a recipient's details, including status, ceremony information and completion timestamp.
- Get upload
Fetches an uploaded file's record by ID: its format, size, hash and expiry. An error occurs if the upload is not found.
- List deliverables
Returns the deliverables (signed PDFs with audit log) of an envelope, earliest first.
- List envelopes
Lists envelopes in the account, most recent first, optionally filtered by status or topic.
- Resend request
Resends the signing request to a recipient who has not yet completed their ceremony, e.g. as a reminder or after a lost or soft-bounced email.
- Update envelope
Update mutable fields (e.g. title, metadata) of an existing envelope.
- Update recipient
Replaces a recipient who has not yet completed with a new person. The original recipient is marked replaced and a new recipient is created with the same type, key, routing position and places.
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 Cal.com
Cal.com to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Cal.com to Cloudflare TraceCloudflare Trace is a free JSON wrapper over Cloudflare's edge trace endpoint that reports what Cloudflare...
Cal.com to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cal.com to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cal.com to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cal.com to Google SheetsGoogle Sheets
More into Signatureapi
Gmail to SignatureapiGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SignatureapiGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Cal.com and Signatureapi, answered
What can start an automation from Cal.com?
Any of Cal.com's 5 triggers in the catalog, including Booking Created, Out of Office Created, Booking Rescheduled and Meeting Ended. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Signatureapi when something happens in Cal.com?
Any of Signatureapi's 15 actions, including Update envelope, Update recipient, Add ceremony and Add deliverable. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Signatureapi to Cal.com?
Signatureapi has no triggers in the catalog today, so automations start in Cal.com. If you need the other direction, ask: your agent reads Signatureapi's API documentation and adds it.
Do I have to build a connector for Cal.com or Signatureapi?
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.
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.