Integration
Connect Casting42 to Code::Stats
When New Casting fires in Casting42, 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 Casting42 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 Casting42 can start in Code::Stats
When New Casting in Casting42
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 Casting42 and Code::Stats
Triggers and actions 6 triggers · 17 actions
- New Casting
Triggers when a casting has been created in your Casting42 Database.
- New Contact
Triggers when a contact has been added to your Casting42 database.
- New Talent
Triggers when a new talent is added in Casting42. Casting42 only shares talents whose "Allow API response" setting is turned on, so talents without it never trigger this.
- Updated Casting
Triggers when the data of a casting has been updated.
- Updated Contact
Triggers when the data of a contact has been updated in your Casting42 database.
- Updated Talent
Triggers when a talent is updated in Casting42. Casting42 only shares talents whose "Allow API response" setting is turned on, so talents without it never trigger this.
- Add File to Talent
Uploads a file such as a resume or PDF document to a talent's profile.
- Add Mediafile to Talent
Uploads a video or audio media file to a talent's profile in Casting42.
- Add Talent to Group
Adds one or more talents to an existing Casting42 group.
- Create Casting
Creates a new casting project in Casting42 and returns it along with its talent sign-up link.
- Create Contact
Creates a new contact in Casting42 with name, email, company, phone, language and address.
- Create Group
Creates a new group in Casting42 for organizing talents.
- Create or Update Candidate
Adds a talent to a casting as a candidate, or updates the candidate's tags if the talent is already in that casting.
- Create Talent
Creates a new talent profile in your Casting42 database and returns the created talent.
- Find Casting
Finds a casting by its tag and returns the full casting record.
- Find Group by Name
Finds a Casting42 group by its name.
- Get Contact
Returns a single Casting42 contact identified by its tag.
- Get Group
Returns a Casting42 group and its talents by the group's tag.
- Get Talent
Returns a single talent record, including custom fields and skills, by its tag.
- Update Casting
Updates an existing casting in Casting42, such as its name, description, dates, locations and sharing options. Fields left blank are not changed.
- Update Contact
Updates an existing contact in Casting42. Only the fields you fill in are changed.
- Update Talent
Updates an existing talent in Casting42, identified by its tag. Fields left blank keep their current values.
- 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 Casting42
Casting42 to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Casting42 to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Casting42 to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Casting42 to Google SheetsGoogle Sheets
Casting42 to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Casting42 to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Code::Stats
Questions
Casting42 and Code::Stats, answered
What can start an automation from Casting42?
Any of Casting42's 6 triggers in the catalog, including New Casting, New Contact, New Talent and Updated Casting. 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 Casting42?
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 Casting42?
Code::Stats has no triggers in the catalog today, so automations start in Casting42. 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 Casting42 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.