Integration
Connect Knorish to Customer.io
When New Signup fires in Knorish, 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 Knorish 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)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 Knorish can start in Customer.io
When New Signup in Knorish
then Send transactional email in Customer.io
When Bundle Purchased in Knorish
then Create Anonymous Event 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 Knorish and Customer.io
Triggers and actions 3 triggers · 37 actions
Trigger
Bundle PurchasedTriggers when a user is newly enrolled in the chosen bundle, such as after purchasing it.
Trigger
Course PurchasedTriggers when a user purchases or is enrolled in the selected Knorish course.
Trigger
New SignupTriggers when a new user signs up on your Knorish site.
Action
Add User to BundleGives a user access to a bundle.
Action
Add User to CourseEnrolls a user in a course.
Action
Create UserCreates a learner account on your Knorish site and returns its id.
Action
Delete BundleRemoves a bundle from your Knorish site.
Action
Delete CourseRemoves a course from your Knorish site.
Action
Delete UserRemoves a user from your Knorish site.
Action
Get BundleReturns a bundle's details by bundle id.
Action
Get CourseReturns a course's details by course id.
Action
Get UserReturns a user's profile by user id.
Action
Get User Course ProgressReturns how far a user has progressed in a course and their average assessment score.
Action
List Bundle CoursesReturns the courses included in a bundle.
Action
List BundlesReturns a page of bundles on your Knorish site.
Action
List Bundle UsersReturns the users who have a bundle, optionally filtered by date range.
Action
List Course AssessmentsReturns a course's assessments with their duration, attempts and pass marks.
Action
List Course Live SessionsReturns a course's live sessions with start/end times and host/join links.
Action
List CoursesReturns a page of courses on your Knorish site.
Action
List Course SectionsReturns a course's sections, including their drip-release settings.
Action
List Course UsersReturns the users enrolled in a course, optionally filtered by enrollment date range.
Action
List Section ChaptersReturns the chapters (lectures) in a course section.
Action
List User BundlesReturns the bundles a user has purchased or been given.
Action
List User CoursesReturns the courses a user is enrolled in, with the date each was assigned.
Action
List User Live SessionsReturns the live sessions available to a user, with start/end times and join links.
Action
List UsersReturns a page of users on your Knorish site, optionally filtered by search text or signup date range.
Action
Remove User From BundleRemoves a user's access to a bundle.
Action
Remove User From CourseRemoves a user's access to a course.
Action
Reply to ContactSends a reply to a contact form submission on your Knorish site.
Action
Update UserUpdates a user's name, email or password.
Action
Create Anonymous EventRecords 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.
Action
Create EventRecords an event for a person in Customer.io, which can trigger campaigns or update segments.
Action
Delete personDeletes a person from your Customer.io workspace, identified by their id, email address or Customer.io id.
Action
Get personLook up a customer's attributes by customer_id.
Action
List segmentsList all manual and data-driven segments in the workspace.
Action
Merge peopleMerges 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.
Action
Remove people from segmentRemoves people from a manual segment in Customer.io. Data-driven segments can't be changed this way.
Action
Send API-triggered broadcastTrigger an API-triggered broadcast campaign to send immediately.
Action
Send transactional emailSend a one-off transactional email via a transactional message template.
Action
Suppress personDeletes 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 Knorish
Knorish to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Knorish to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Knorish to MailchimpMailchimp marketing automation and email platform.
Knorish to StripeStripe is a payment processing platform for online businesses.
Knorish to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Knorish to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
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.
Salesforce to Customer.ioSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Customer.ioSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
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
Knorish and Customer.io, answered
What can start an automation from Knorish?
Any of Knorish's 3 triggers in the catalog, including New Signup, Bundle Purchased and Course Purchased. 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 Knorish?
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 Knorish?
Customer.io has no triggers in the catalog today, so automations start in Knorish. 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 Knorish 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 Knorish 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.