Integration
Connect ProspectPro to Code::Stats
When New Contact fires in ProspectPro, your agent runs Get user in Code::Stats. 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 ProspectPro and Code::Stats to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 ProspectPro can start in Code::Stats
When New Contact in ProspectPro
then Get user in Code::Stats
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 ProspectPro and Code::Stats
Triggers and actions 2 triggers · 11 actions
- New Contact
Triggers when a new contact is created
- New or Updated Contact
Triggers when a Contact is created or updated.
- Add contact
Create a contact on a prospect.
- Add event
Add an event to a prospect.
- Delete contact
Delete a contact.
- Delete event
Delete an event.
- Get Contacts
Get Contacts from ProspectPro.
- Get Prospect
Get a specific prospect by ID.
- List events
List events.
- Update contact
Edit a contact.
- Update Tags
Update the tags associated with a specific prospect.
- Update Target Audience Status
Update the target audience status for a specific prospect.
- Get user
Retrieve a public user's profile (total XP, new XP in last 12h, per-machine, per-language and per-date XP).
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 ProspectPro
ProspectPro to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
ProspectPro to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
ProspectPro to StripeStripe is a payment processing platform for online businesses.
ProspectPro to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
ProspectPro to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
ProspectPro to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
More into Code::Stats
HubSpot to Code::StatsHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Code::StatsGoogle Sheets
Gmail to Code::StatsGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Code::StatsGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
ProspectPro and Code::Stats, answered
What can start an automation from ProspectPro?
Any of ProspectPro's 2 triggers in the catalog, including New Contact and New or Updated Contact. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Code::Stats when something happens in ProspectPro?
Any of Code::Stats's 1 action, including Get user. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Code::Stats to ProspectPro?
Code::Stats has no triggers in the catalog today, so automations start in ProspectPro. If you need the other direction, ask: your agent reads Code::Stats's API documentation and adds it.
Do I have to build a connector for ProspectPro or Code::Stats?
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.
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.