Integration
Connect Pleo to Customer.io
When New Employee fires in Pleo, your agent runs Send transactional email in Customer.io. 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 Pleo and Customer.io 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 Pleo can start in Customer.io
When New Employee in Pleo
then Send transactional email in Customer.io
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 Pleo and Customer.io
Triggers and actions 2 triggers · 34 actions
- New Employee
Triggered when a new employee is added in Pleo.
- New Tag
Triggers when a new tag is added to the selected tag group.
- Add account
Creates an account in a Pleo company's chart of accounts, matching a record in your accounting system, and returns the new account.
- Add tag group
Creates a new tag group (a cost-centre dimension such as Projects or Departments) in Pleo.
- Add tax code
Creates a tax code in a Pleo company, with its name, rate and type.
- Add team
Creates a new team in a Pleo company or organisation and returns the created team.
- Create Tag
Creates a new tag in a Pleo tag group, such as a cost centre or project, and returns the created tag.
- Delete tag
Deletes a tag from Pleo by its ID.
- Delete tag group
Deletes a tag group from Pleo by its ID.
- Delete tax code
Deletes a tax code from a Pleo company.
- Get an Employee
Returns one Pleo employee by ID, including their name, email, job title, phone, role, company and avatar.
- Get company balance
Returns the current balance of every Pleo account belonging to a company, including available funds, pending debits and overdraft.
- Get Expense
Returns a single Pleo expense (accounting entry) by its ID, including its amounts, merchant, category, tags, review and export status, and receipt IDs.
- Get tag
Returns a Pleo tag by its ID, including its name, code, tag group and archived status.
- Get tag group
Returns a tag group by its ID, including its name, code, archived status, metadata and total number of tags.
- Get Tax Code
Returns a single tax code from Pleo, including its name, rate, type and archived status.
- Get team
Returns a Pleo team by its ID, including its name, code, company, organisation and employee IDs. An error occurs if the team is not found.
- List accounts
Returns the accounts in a Pleo company's chart of accounts, optionally narrowed by name, code, external ID, account ID or archived status.
- List employees
Returns the employees in your Pleo company, optionally filtered by company, email or external ID.
- List tag groups
Returns the tag groups for a Pleo company, or for all companies in an organisation.
- List tags
Returns the tags in a Pleo tag group, optionally including archived tags.
- List tax codes
Returns the tax codes for a Pleo company, optionally filtered by code, type, archived status or specific tax code IDs.
- List teams
Returns the teams in a Pleo company or organisation, optionally filtered by name, member employee or team.
- Update tag
Updates a tag's code, name, archived state and additional dimension values in Pleo, and returns the updated tag.
- Update tag group
Updates a tag group's name, code, archived status and metadata. All values replace the tag group's current ones.
- Update tax code
Updates an existing tax code in Pleo, including its name, rate, type and archived status, and returns the updated tax code.
- Create Anonymous Event
Records an event that isn't tied to a known person yet, such as a page view or an action by a visitor. Include an anonymous id to link the event to a person later.
- Create Event
Records an event for a person in Customer.io, which can trigger campaigns or update segments.
- Delete person
Deletes a person from your Customer.io workspace, identified by their id, email address or Customer.io id.
- Get person
Look up a customer's attributes by customer_id.
- List segments
List all manual and data-driven segments in the workspace.
- Merge people
Merges a duplicate person into a primary person. The secondary person's attributes and activity move to the primary person, and the secondary person is deleted.
- Remove people from segment
Removes people from a manual segment in Customer.io. Data-driven segments can't be changed this way.
- Send API-triggered broadcast
Trigger an API-triggered broadcast campaign to send immediately.
- Send transactional email
Send a one-off transactional email via a transactional message template.
- Suppress person
Deletes a person from your Customer.io workspace and suppresses their identifiers so nobody can be added again with the same id, email or phone. Activity attributed to them is redacted.
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 Pleo
Pleo to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pleo to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Pleo to StripeStripe is a payment processing platform for online businesses.
Pleo to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Pleo to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Pleo to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into Customer.io
HubSpot to Customer.ioHubSpot is your all-in-one stop for all of your marketing software needs.
Wistia to Customer.ioWistia makes it easy to host, track, and measure video engagement online.
Google Sheets to Customer.ioGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Customer.ioGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Pleo and Customer.io, answered
What can start an automation from Pleo?
Any of Pleo's 2 triggers in the catalog, including New Employee and New Tag. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Customer.io when something happens in Pleo?
Any of Customer.io's 10 actions, including Create Anonymous Event, Create Event, Send API-triggered broadcast and Send transactional email. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Customer.io to Pleo?
Customer.io has no triggers in the catalog today, so automations start in Pleo. If you need the other direction, ask: your agent reads Customer.io's API documentation and adds it.
Do I have to build a connector for Pleo or Customer.io?
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 Pleo and Customer.io 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.