Integration
Connect Mateo and Pyrus
When Contact Created fires in Mateo, your agent runs Add Task Comment in Pyrus, or New Form Task in Pyrus to Add Contact to List in Mateo. 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 Mateo and Pyrus 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 Mateo and Pyrus can do together
From Mateo to Pyrus
When Contact Created in Mateo
then Add Task Comment in Pyrus
When Contact Details Updated in Mateo
then Find Form Tasks in Pyrus
From Pyrus to Mateo
When New Form Task in Pyrus
then Add Contact to List in Mateo
When New Form Task in Pyrus
then Create Contact Details in Mateo
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 Mateo and Pyrus
Triggers and actions 7 triggers · 41 actions
Trigger
Contact CreatedTriggers when a new contact is created in hellomateo.
Trigger
Contact Details UpdatedTriggers when a contact is created or its details are updated.
Trigger
Inbound MessageTriggers when a new inbound message arrives from a contact.
Trigger
New AppointmentTriggers when a new appointment is created.
Trigger
New ConversationTriggers when a new conversation starts.
Trigger
New DealTriggers when a new deal is created.
Action
Add Contact to ListAdds a contact to a contact list.
Action
Add Conversation CommentAdds an internal comment to a conversation.
Action
Assign ConversationAssigns a conversation to an employee or agent.
Action
Close ConversationCloses a conversation.
Action
Create AppointmentCreates an appointment for a contact.
Action
Create Contact DetailsCreates a new contact with name, address and external IDs.
Action
Create Contact ListCreates a contact list.
Action
Create DealCreates a deal for a contact.
Action
Delete ContactDeletes a contact.
Action
Delete DealDeletes a deal.
Action
Find ChannelReturns the messaging channels (WhatsApp, SMS, email and others) in the account.
Action
Find ContactFinds one contact by exactly one locator: email, phone number, external ID or social ID.
Action
Find Contact DetailsReturns a contact by its hellomateo ID.
Action
Find Custom FieldReturns the custom fields defined in the account.
Action
Find MessageReturns a message by its ID.
Action
Find TemplateReturns the message templates in the account.
Action
Format a Phone NumberFormats a phone number to E.164.
Action
Get AppointmentReturns an appointment by ID.
Action
Get ConversationReturns a conversation by ID.
Action
Get DealReturns a deal by ID.
Action
List Contact ListsReturns the contact lists in the account.
Action
List ContactsReturns contacts, optionally filtered by external ID or last update time.
Action
List EmployeesReturns the employees in the organisation.
Action
Open ConversationReopens a closed conversation.
Action
Remove Contact from ListRemoves a contact from a contact list.
Action
Send Template MessageSends a template message to a contact on a hellomateo channel.
Action
Send Text MessageSends a free-text message to a contact on a hellomateo channel.
Action
Start JourneyStarts a journey for a contact, matching or creating the contact by external ID.
Action
Update Contact DetailsUpdates an existing contact's name, address and other details.
Action
Update DealUpdates a deal's name, status, value or assignee.
Trigger
New Form TaskTriggers when a new task is created from a Pyrus form.
Action
Add MemberAdds a user to the Pyrus organization.
Action
Add Task CommentAdds a comment to a Pyrus task, and can also close or reopen it, approve or reject it, or reassign it.
Action
Delete TaskDeletes a Pyrus task.
Action
Find Catalog ItemsReturns a Pyrus catalog's items, optionally only those whose column matches a value.
Action
Find Form TasksSearches the tasks created from a Pyrus form, by text, step, or creation and modification dates.
Action
Get FormReturns a Pyrus form template with its fields.
Action
Get MemberReturns a Pyrus organization member's profile by ID.
Action
Get TaskReturns a Pyrus task with its fields, participants and comments.
Action
List CatalogsReturns all Pyrus catalogs, without their items.
Action
List FormsReturns all Pyrus form templates the user manages or belongs to.
Action
List MembersReturns all members of the Pyrus organization.
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 Mateo
Mateo to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Mateo to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Mateo to StripeStripe is a payment processing platform for online businesses.
Mateo to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Mateo to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Mateo to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Pyrus
HubSpot to PyrusHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PyrusGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PyrusGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PyrusGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PyrusGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PyrusMailchimp marketing automation and email platform.
Questions
Mateo and Pyrus, answered
What can start an automation from Mateo?
Any of Mateo's 6 triggers in the catalog, including Contact Created, Contact Details Updated, New Appointment and New Conversation. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pyrus when something happens in Mateo?
Any of Pyrus's 11 actions, including Add Member, Add Task Comment, Find Catalog Items and Find Form Tasks. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pyrus to Mateo?
Yes. When something happens in Pyrus, your agent can act in Mateo too. This page covers both directions: Pyrus's triggers and Mateo's actions are listed here as well.
Do I have to build a connector for Mateo or Pyrus?
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 Mateo and Pyrus 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.