--- title: "Connect Pipefy to SignRequest - APIANT.ai" description: "When \"Moved Card\" fires in Pipefy, your agent runs \"Add document\" in SignRequest." canonical: "https://apiant.ai/connect/pipefy-to-signrequest" --- # Connect Pipefy to SignRequest When **Moved Card** fires in [Pipefy](https://apiant.ai/connections/pipefy), your agent runs **Add document** in [SignRequest](https://apiant.ai/connections/signrequest). Describe the whole flow and it is built, tested on every scenario and kept running. Pipefy **6** triggers Pipefy **11** actions SignRequest **12** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Pipefy and SignRequest 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 Pipefy can start in SignRequest - When **Moved Card** in Pipefy then **Add document** in SignRequest - When **New Card** in Pipefy then **Add document attachment** in SignRequest 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 Pipefy and SignRequest ## Triggers and actions 6 triggers · 23 actions - Trigger **Done Card** Triggers when a card is done. - Trigger **Moved Card** Triggers when a card is moved. - Trigger **New Card** Triggers when a new card is created. - Trigger **New Database Record** Triggers when a new record is created. - Trigger **Updated Card Field** Triggers when a card field is updated. - Trigger **Updated Record Field** Triggers when a record field is updated. - Action **Create Card** Creates a card in a Pipefy pipe, filling in its start form fields. - Action **Create Record** Creates a new table record. - Action **Delete Card** Permanently deletes a card from its pipe. - Action **Delete Database Record** Delete a database table record by ID via the GraphQL `deleteTableRecord(input: {id})` mutation. - Action **Find Card** Returns the cards in a pipe whose chosen field matches the specified value. - Action **Find Database Records** Find a database records by title. - Action **Get Card** Retrieves a single Pipefy card by its id, including its phase, pipe, assignees, labels, attachments and field values. - Action **Get Database Record** Fetch a single database table record by ID via the GraphQL `table_record(id: ID)` query. - Action **Move Card** Moves a Pipefy card to another phase of its pipe. - Action **Update Card Field** Sets a new value on one field of an existing Pipefy card. - Action **Update Database Record** Update a database table record's title/fields via the GraphQL `updateTableRecord(input: {id, title})` mutation. - Action **Add document** Creates a document in SignRequest from a file link, uploaded file content or a template, ready to be sent out for signature. - Action **Add document attachment** Attaches a file to an existing SignRequest document, from a public link or from the file's contents. - Action **Cancel SignRequest** Cancels a SignRequest that is still pending, so its signers can no longer sign the document. - Action **Delete document** Deletes a document from your SignRequest team. - Action **Get document** Returns a single SignRequest document by its ID, including its status, signers, and temporary links to the original and signed PDFs. - Action **Get SignRequest** Returns a SignRequest by its ID, including its signers and their signing status, the email subject and message, and the linked document. - Action **List documents** Returns the documents in your SignRequest team, optionally filtered by status, external ID, sender, owner or date. - Action **List SignRequests** Returns the signature requests in your SignRequest team, optionally filtered by sender email or by who signs. - Action **List templates** Returns the templates available to your SignRequest team, with each template's name, ID and signer setup. - Action **Resend SignRequest** Resends the signature request email to the signers of an existing SignRequest who have not yet signed. - Action **Send SignRequest** Sends an existing SignRequest document out for signature to one or more signers, and returns the new SignRequest. - Action **Send SignRequest From Template** Creates a document from one of your SignRequest templates and sends it to the signers you choose in a single step. Returns the new SignRequest with its signers and document. ## Each app on its own - [ **Pipefy** The easy button for processes and workflows Easily organize and run all your processes in one place, leaving...](https://apiant.ai/connections/pipefy) - [ **SignRequest** SignRequest is an electronic (digital) signature solution to get documents signed.](https://apiant.ai/connections/signrequest) Reviews ## What our customers say ## More from Pipefy - [ **Pipefy to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/pipefy-to-trello) - [ **Pipefy to Spaceflight News** Spaceflight News API aggregates news coverage of spaceflight and the space industry from many publishers.](https://apiant.ai/connect/pipefy-to-spaceflight-news) - [ **Pipefy to SparrowDesk** SparrowDesk is an AI-first helpdesk that unifies customer support across email & chat while automating...](https://apiant.ai/connect/pipefy-to-sparrowdesk) - [ **Pipefy to Timing** Timing is an automatic time tracking app for macOS.](https://apiant.ai/connect/pipefy-to-timing) - [ **Pipefy to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/pipefy-to-salesforce) - [ **Pipefy to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/pipefy-to-slack) ## More into SignRequest - [ **HubSpot to SignRequest** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-signrequest) - [ **Salesforce to SignRequest** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-signrequest) - [ **Slack to SignRequest** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-signrequest) - [ **Google Sheets to SignRequest** Google Sheets](https://apiant.ai/connect/google-sheets-to-signrequest) - [ **Gmail to SignRequest** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-signrequest) - [ **Google Calendar to SignRequest** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-signrequest) Questions ## Pipefy and SignRequest, answered ### ### What can start an automation from Pipefy? Any of Pipefy's 6 triggers in the catalog, including Moved Card, New Card, New Database Record and Updated Card Field. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in SignRequest when something happens in Pipefy? Any of SignRequest's 12 actions, including Send SignRequest, Send SignRequest From Template, Add document and Add document attachment. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from SignRequest to Pipefy? SignRequest has no triggers in the catalog today, so automations start in Pipefy. If you need the other direction, ask: your agent reads SignRequest's API documentation and adds it. ### ### Do I have to build a connector for Pipefy or SignRequest? 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 Pipefy and SignRequest 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.