Integration
Connect Azure DevOps and Text Request
When Completed Build fires in Azure DevOps, your agent runs Add group message in Text Request, or New Contact in Text Request to Add Link to Work Item in Azure DevOps. 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 Azure DevOps and Text Request 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 Azure DevOps and Text Request can do together
From Azure DevOps to Text Request
When Completed Build in Azure DevOps
then Add group message in Text Request
From Text Request to Azure DevOps
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 Text Request
Triggers and actions 7 triggers · 28 actions
- Code Push (Git)
Triggers when commits are pushed to a Git repository in an Azure DevOps project.
- Completed Build
Triggers when a build finishes in an Azure DevOps project, with its result (succeeded, failed, partially succeeded or canceled).
- New Work Item
Triggers when a work item is created in an Azure DevOps project.
- New Work Item Comment
Triggers when someone comments on a work item in an Azure DevOps project.
- 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.
- 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.
- Create Work Item
Creates a new work item (such as a Task, Bug, Issue or User Story) in an Azure DevOps project.
- 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.
- 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.
- 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.
- New Contact
Triggers when a new contact is added to a dashboard.
- New Message
Triggers when a text message is sent or received on a dashboard.
- Add custom field
Creates a new custom field on a Text Request dashboard, which can then be set on contacts.
- Add group message
Sends a group text message to selected groups and/or phone numbers from a dashboard, immediately, at a scheduled time, or on a recurring schedule.
- Add keyword
Creates a new keyword on a Text Request dashboard, with an optional automatic reply sent when a contact texts it.
- Add payment
Sends a payment request text to a contact for the given amount and returns the new payment.
- Add user
Creates a new user in your Text Request account with the given name, email and password, optionally granting administrator rights or dashboard permissions.
- Create Group
Creates a contact group on a dashboard.
- Create Tag
Creates a contact tag on a dashboard.
- Delete Contact
Deletes a contact from a dashboard by their phone number.
- Delete group
Deletes a group from a dashboard. Contacts in the group are kept.
- Delete tag
Deletes a contact tag from a Text Request dashboard. Contacts that carried the tag are not deleted.
- Find Contacts
Finds contacts on a dashboard by name, phone number, tag or group.
- Get Contact
Returns one contact on a dashboard by their phone number, including name, tags, groups, custom fields and message counts.
- Get dashboard
Returns a dashboard (texting line) with its name, phone number and time zone.
- List custom fields
Returns all custom fields defined for a Text Request dashboard (texting line), with each field's id and name.
- List Dashboards
Returns every dashboard (texting phone line) in your Text Request account, with its ID, name and phone number.
- List Groups
Returns all contact groups on a dashboard.
- List keywords
Returns all keywords on a Text Request dashboard, with their auto-response, linked group and subscriber count.
- List messages
Returns the text messages sent and received on a Text Request dashboard, optionally filtered by date range.
- List scheduled messages
Returns the pending scheduled one-to-one messages for a dashboard, optionally filtered by send time or to recurring messages only.
- List tags
Returns all contact tags defined on a Text Request dashboard, with each tag's name and color.
- List users
Returns the users in your Text Request account, optionally filtered by email or external user ID.
- Send Message
Sends a text message from a dashboard to a contact's phone number, now or at a scheduled time.
- Update group
Renames a group on a Text Request dashboard and updates its notes.
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 Azure DevOps
Azure DevOps to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Azure DevOps to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Azure DevOps to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Azure DevOps to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Azure DevOps to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Azure DevOps to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Text Request
Questions
Azure DevOps and Text Request, 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 Text Request when something happens in Azure DevOps?
Any of Text Request's 23 actions, including Create Group, Create Tag, Send Message and Update group. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Text Request to Azure DevOps?
Yes. When something happens in Text Request, your agent can act in Azure DevOps too. This page covers both directions: Text Request's triggers and Azure DevOps's actions are listed here as well.
Do I have to build a connector for Azure DevOps or Text Request?
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 Text Request 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.