Integration
Connect kvCORE to Disciple
When New Lead fires in kvCORE, your agent runs Create User in Disciple. 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 kvCORE and Disciple 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 kvCORE can start in Disciple
When New Lead in kvCORE
then Create User in Disciple
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 kvCORE and Disciple
Triggers and actions 2 triggers · 18 actions
- New Lead
Triggers when a new lead (contact) is registered in kvCORE.
- New User (Polling)
Triggers when a new user appears in your Disciple community.
- Create Group
Creates a group in your Disciple community and returns it.
- Create Group Member
Adds a user to a Disciple group as a member or group admin.
- Create Subscription Preregistration
Preregisters a subscription for an email so it is assigned when that person signs up.
- Create User
Creates a new user in your Disciple community and returns the user.
- Create User Subscription
Gives a Disciple user a subscription that runs until the expiry date.
- Delete User
Schedules deletion of a Disciple user.
- Expire User Subscription
Expires a subscription a Disciple user owns.
- Find Users by Email
Finds Disciple users whose email exactly matches the one given.
- Get User
Returns one Disciple user by their ID.
- List Badges
Returns all custom badges in your Disciple community.
- List Groups
Returns all groups in your Disciple community.
- List Products
Returns all products in your Disciple community.
- List Subscriptions
Returns all subscriptions offered in your Disciple community.
- List Users
Returns a page of users in your Disciple community with the total user count.
- Reactivate User
Reactivates a disabled Disciple user.
- Remove Group Member
Removes a user from a Disciple group.
- Send Push Notification
Sends a push notification to all users, or to the users matching a filter query.
- Unpublish Post
Unpublishes a Disciple post.
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 kvCORE
kvCORE to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
kvCORE to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
kvCORE to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
kvCORE to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
kvCORE to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
kvCORE to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Disciple
ActiveCampaign to DiscipleActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to DiscipleOrganize anything with Airtable, a modern database created for everyone.
Asana to DiscipleAsana is a collaborative information manager for workspace.
ClickUp to DiscipleClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Brevo to DiscipleBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to DiscipleCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
Questions
kvCORE and Disciple, answered
What can start an automation from kvCORE?
Any of kvCORE's 1 trigger in the catalog, including New Lead. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Disciple when something happens in kvCORE?
Any of Disciple's 18 actions, including Create Group, Create Group Member, Create Subscription Preregistration and Create User. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Disciple to kvCORE?
Disciple has no triggers in the catalog today, so automations start in kvCORE. If you need the other direction, ask: your agent reads Disciple's API documentation and adds it.
Do I have to build a connector for kvCORE or Disciple?
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 kvCORE and Disciple without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in Disciple 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.