Integration
Connect Kit to Reach 360
When New Form Subscriber fires in Kit, your agent runs Find a User in Reach 360. 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 Kit and Reach 360 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 Kit can start in Reach 360
When New Form Subscriber in Kit
then Find a User in Reach 360
When New Purchase in Kit
then Get user in Reach 360
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 Kit and Reach 360
Triggers and actions 7 triggers · 10 actions
Trigger
New Form SubscriberTriggers when a subscription occurs on a specific form.
Trigger
New PurchaseTriggers when a new purchase is added to your account.
Trigger
New Sequence SubscriberTriggers when a subscriber is added to a sequence.
Trigger
New SubscriberTriggers when a new subscriber is confirmed within your account (has completed any applicable double opt-ins).
Trigger
New UnsubscribeTriggers when a subscriber unsubscribes from your emails.
Trigger
Subscriber Added to TagTriggers when a specific tag is added to a subscriber.
Trigger
Tag Removed From SubscriberTriggers when a specific tag is removed from a subscriber.
Action
Add Subscriber to FormSubscribe someone to a specific form.
Action
Add Tag to SubscriberAdd a subscriber to a specific tag.
Action
Find SubscriberFinds an existing confirmed subscriber by email.
Action
Remove Tag From SubscriberRemove a specific tag from a subscriber if they have it.
Action
Create InvitationSends an invitation to a person to join your Reach 360 team, optionally with their name and the groups they should join.
Action
Find an InvitationFinds pending Reach 360 invitations for an email address.
Action
Find a UserFinds a Reach 360 user by email address and returns their profile, role and report links.
Action
Get learner reportReturns the courses a Reach 360 learner is enrolled in, with status, progress, quiz score, due and completion dates for each.
Action
Get userReturns the details of a single Reach 360 user, including email, name, role and last activity time.
Action
List usersReturns the users in your Reach 360 account, optionally only those with a given email address.
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 Kit
Kit to API SnapFree utility API platform. QR codes, screenshots, PDFs, image resize, hashing, and more
Kit to ClerkClerk is a user authentication and management platform that lets developers add sign-in, profiles, and...
Kit to PostLakeOne API to publish, schedule, and read analytics across every major social network
Kit to SynchroteamSynchroteam is a Cloud-based Field Service Management application
Kit to WikimediaThis API provides cacheable and straightforward access to Wikimedia content and data, in machine-readable...
Kit to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
More into Reach 360
HubSpot to Reach 360HubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Reach 360Salesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Reach 360Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Reach 360Google Sheets
Gmail to Reach 360Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Reach 360Google Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Kit and Reach 360, answered
What can start an automation from Kit?
Any of Kit's 7 triggers in the catalog, including New Form Subscriber, New Purchase, New Sequence Subscriber and New Subscriber. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Reach 360 when something happens in Kit?
Any of Reach 360's 6 actions, including Create Invitation, Find an Invitation, Find a User and Get learner report. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Reach 360 to Kit?
Reach 360 has no triggers in the catalog today, so automations start in Kit. If you need the other direction, ask: your agent reads Reach 360's API documentation and adds it.
Do I have to build a connector for Kit or Reach 360?
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 Kit and Reach 360 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.