--- title: "Connect Azure DevOps to SignRequest - APIANT.ai" description: "When \"Completed Build\" fires in Azure DevOps, your agent runs \"Add document\" in SignRequest." canonical: "https://apiant.ai/connect/azure-devops-to-signrequest" --- # Connect Azure DevOps to SignRequest When **Completed Build** fires in [Azure DevOps](https://apiant.ai/connections/azure-devops), 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. Azure DevOps **5** triggers Azure DevOps **5** actions SignRequest **13** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Azure DevOps 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 Azure DevOps can start in SignRequest - When **Completed Build** in Azure DevOps then **Add document** in SignRequest - When **New Work Item** in Azure DevOps 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 Azure DevOps and SignRequest ## Triggers and actions 5 triggers · 18 actions - Trigger **Code Push (Git)** Triggers when commits are pushed to a Git repository in an Azure DevOps project. - Trigger **Completed Build** Triggers when a build finishes in an Azure DevOps project, with its result (succeeded, failed, partially succeeded or canceled). - Trigger **New Work Item** Triggers when a work item is created in an Azure DevOps project. - Trigger **New Work Item Comment** Triggers when someone comments on a work item in an Azure DevOps project. - Trigger **Updated Work Item** Triggers when a work item is updated in an Azure DevOps project, with the work item's current values and the list of fields that changed. - Action **Add Link to Work Item** Adds a link to an Azure DevOps work item: a related, parent, child, predecessor, successor or duplicate link to another work item, or a hyperlink to a web page. - Action **Create Work Item** Creates a new work item (such as a Task, Bug, Issue or User Story) in an Azure DevOps project. - Action **Find Work Item** Finds work items in an Azure DevOps project that match a Work Item Query Language (WIQL) query, returning the matching work item IDs, or the matching links for a link query. - Action **Trigger Build** Queues a new run of an Azure DevOps build pipeline, optionally for a specific branch or commit and with pipeline variables or parameters. - Action **Update Work Item** Updates an existing Azure DevOps work item: changes its title, description, state, assignee, area, iteration, priority or tags, and can add a discussion comment. Fields left blank are not changed. - 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 **Find documents by criteria** Returns up to 100 SignRequest documents that match a search query, document name, signer email, status or ownership filter, newest or best match first. - 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 - [ **Azure DevOps** Azure DevOps is where teams manage, develop, and deliver software in the cloud.](https://apiant.ai/connections/azure-devops) - [ **SignRequest** SignRequest is an electronic (digital) signature solution to get documents signed.](https://apiant.ai/connections/signrequest) Reviews ## What our customers say ## More from Azure DevOps - [ **Azure DevOps to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/azure-devops-to-hubspot) - [ **Azure DevOps to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/azure-devops-to-salesforce) - [ **Azure DevOps to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/azure-devops-to-slack) - [ **Azure DevOps to Google Sheets** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/azure-devops-to-google-sheets) - [ **Azure DevOps to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/azure-devops-to-gmail) - [ **Azure DevOps to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/azure-devops-to-google-calendar) ## 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 is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](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 ## Azure DevOps and SignRequest, answered ### ### What can start an automation from Azure DevOps? Any of Azure DevOps's 5 triggers in the catalog, including Completed Build, New Work Item, New Work Item Comment and Updated Work Item. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in SignRequest when something happens in Azure DevOps? Any of SignRequest's 13 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 Azure DevOps? SignRequest has no triggers in the catalog today, so automations start in Azure DevOps. 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 Azure DevOps 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 Azure DevOps 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.