--- title: "Connect GSMtasks to Signatureapi - APIANT.ai" description: "When \"New task event\" fires in GSMtasks, your agent runs \"Add ceremony\" in Signatureapi." canonical: "https://apiant.ai/connect/gsmtasks-to-signatureapi" --- # Connect GSMtasks to Signatureapi When **New task event** fires in [GSMtasks](https://apiant.ai/connections/gsmtasks), your agent runs **Add ceremony** in [Signatureapi](https://apiant.ai/connections/signatureapi). Describe the whole flow and it is built, tested on every scenario and kept running. GSMtasks **1** trigger GSMtasks **8** actions Signatureapi **15** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want GSMtasks and Signatureapi to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What GSMtasks can start in Signatureapi - When **New task event** in GSMtasks then **Add ceremony** in Signatureapi - When **New task event** in GSMtasks then **Add deliverable** 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 GSMtasks and Signatureapi ## Triggers and actions 1 trigger · 23 actions - Trigger **New task event** Triggers when a new event is recorded on a task, such as creation, assignment, acceptance, completion, failure or cancellation. - Action **Add client** Creates a new client in your GSMtasks account. - Action **Add contact address** Creates a contact address (a saved contact with its address) in GSMtasks. - Action **Add task** Creates a new task in GSMtasks with its address, contact, time window and assignment details. - Action **Assign task** Assigns a GSMtasks task to a worker, optionally with notes and the location where the assignment happened. - Action **Cancel task** Cancels a GSMtasks task, optionally recording a note and the location where it was cancelled. - Action **Complete task** Marks a GSMtasks task as completed, optionally with completion notes and the location where it was completed. - Action **Get contact address** Returns a single contact address, with its address and contact details. - Action **Update task** Updates an existing GSMtasks task, changing only the details you fill in such as its address, contact, schedule, assignee or description. - Action **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. - Action **Add deliverable** Creates an additional deliverable (signed PDF package) from a completed envelope. The envelope must be completed. - Action **Add envelope** Creates an envelope with documents and recipients and starts the signing process. - Action **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. - Action **Cancel envelope** Cancel an in-progress envelope so remaining recipients can no longer sign. - Action **Delete envelope** Delete an envelope. - Action **Get deliverable** Retrieves a deliverable by its ID, including its status and, once generated, a download link for the signed PDF. - Action **Get envelope** Retrieve a single envelope by id. - Action **Get recipient** Retrieves a recipient's details, including status, ceremony information and completion timestamp. - Action **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. - Action **List deliverables** Returns the deliverables (signed PDFs with audit log) of an envelope, earliest first. - Action **List envelopes** Lists envelopes in the account, most recent first, optionally filtered by status or topic. - Action **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. - Action **Update envelope** Update mutable fields (e.g. title, metadata) of an existing envelope. - Action **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. ## Each app on its own - [ **GSMtasks** The GSMtasks API is a RESTful web service for developers to programmatically interact with GSMtasks data...](https://apiant.ai/connections/gsmtasks) - [ **Signatureapi** API for generating documents from templates and collecting legally binding electronic signatures.](https://apiant.ai/connections/signatureapi) Reviews ## What our customers say ## More from GSMtasks - [ **GSMtasks to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/gsmtasks-to-hubspot) - [ **GSMtasks to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/gsmtasks-to-salesforce) - [ **GSMtasks to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/gsmtasks-to-slack) - [ **GSMtasks to Mailchimp** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/gsmtasks-to-mailchimp) - [ **GSMtasks to Stripe** Stripe is a payment processing platform for online businesses.](https://apiant.ai/connect/gsmtasks-to-stripe) - [ **GSMtasks to Shopify** Shopify is a commerce platform for online stores and retail point-of-sale.](https://apiant.ai/connect/gsmtasks-to-shopify) ## More into Signatureapi - [ **HubSpot to Signatureapi** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-signatureapi) - [ **Salesforce to Signatureapi** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-signatureapi) - [ **Slack to Signatureapi** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-signatureapi) - [ **Google Sheets to Signatureapi** Google Sheets](https://apiant.ai/connect/google-sheets-to-signatureapi) - [ **Gmail to Signatureapi** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-signatureapi) - [ **Google Calendar to Signatureapi** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-signatureapi) Questions ## GSMtasks and Signatureapi, answered ### ### What can start an automation from GSMtasks? Any of GSMtasks's 1 trigger in the catalog, including New task event. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Signatureapi when something happens in GSMtasks? 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 GSMtasks? Signatureapi has no triggers in the catalog today, so automations start in GSMtasks. 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 GSMtasks 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. ### ### Can my AI client use GSMtasks and Signatureapi 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.