Integration
Connect Azure DevOps and Mateo
When Completed Build fires in Azure DevOps, your agent runs Add Contact to List in Mateo, or Contact Created in Mateo 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 Mateo 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Mateo can do together
From Azure DevOps to Mateo
When Completed Build in Azure DevOps
then Add Contact to List in Mateo
From Mateo 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 Mateo
Triggers and actions 11 triggers · 35 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.
- Contact Created
Triggers when a new contact is created in hellomateo.
- Contact Details Updated
Triggers when a contact is created or its details are updated.
- Inbound Message
Triggers when a new inbound message arrives from a contact.
- New Appointment
Triggers when a new appointment is created.
- New Conversation
Triggers when a new conversation starts.
- New Deal
Triggers when a new deal is created.
- Add Contact to List
Adds a contact to a contact list.
- Add Conversation Comment
Adds an internal comment to a conversation.
- Assign Conversation
Assigns a conversation to an employee or agent.
- Close Conversation
Closes a conversation.
- Create Appointment
Creates an appointment for a contact.
- Create Contact Details
Creates a new contact with name, address and external IDs.
- Create Contact List
Creates a contact list.
- Create Deal
Creates a deal for a contact.
- Delete Contact
Deletes a contact.
- Delete Deal
Deletes a deal.
- Find Channel
Returns the messaging channels (WhatsApp, SMS, email and others) in the account.
- Find Contact
Finds one contact by exactly one locator: email, phone number, external ID or social ID.
- Find Contact Details
Returns a contact by its hellomateo ID.
- Find Custom Field
Returns the custom fields defined in the account.
- Find Message
Returns a message by its ID.
- Find Template
Returns the message templates in the account.
- Format a Phone Number
Formats a phone number to E.164.
- Get Appointment
Returns an appointment by ID.
- Get Conversation
Returns a conversation by ID.
- Get Deal
Returns a deal by ID.
- List Contact Lists
Returns the contact lists in the account.
- List Contacts
Returns contacts, optionally filtered by external ID or last update time.
- List Employees
Returns the employees in the organisation.
- Open Conversation
Reopens a closed conversation.
- Remove Contact from List
Removes a contact from a contact list.
- Send Template Message
Sends a template message to a contact on a hellomateo channel.
- Send Text Message
Sends a free-text message to a contact on a hellomateo channel.
- Start Journey
Starts a journey for a contact, matching or creating the contact by external ID.
- Update Contact Details
Updates an existing contact's name, address and other details.
- Update Deal
Updates a deal's name, status, value or assignee.
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 Mateo
Google Drive to MateoGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to MateoMailchimp marketing automation and email platform.
Questions
Azure DevOps and Mateo, 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 Mateo when something happens in Azure DevOps?
Any of Mateo's 30 actions, including Create Appointment, Create Contact Details, Create Contact List and Create Deal. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Mateo to Azure DevOps?
Yes. When something happens in Mateo, your agent can act in Azure DevOps too. This page covers both directions: Mateo's triggers and Azure DevOps's actions are listed here as well.
Do I have to build a connector for Azure DevOps or Mateo?
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 Mateo 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.