Integration
Connect Casting42 and GitHub
When New Casting fires in Casting42, your agent runs Add Labels to Issue in GitHub, or New Branch in GitHub to Create Contact in Casting42. 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 GitHub 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 and GitHub can do together
From Casting42 to GitHub
When New Casting in Casting42
then Add Labels to Issue in GitHub
When New Contact in Casting42
then Create Issue in GitHub
From GitHub to Casting42
When New Branch in GitHub
then Create Contact in Casting42
When New Collaborator in GitHub
then Add File to Talent in Casting42
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 GitHub
Triggers and actions 21 triggers · 35 actions
Trigger
New CastingTriggers when a casting has been created in your Casting42 Database.
Trigger
New ContactTriggers when a contact has been added to your Casting42 database.
Trigger
New TalentTriggers 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.
Trigger
Updated CastingTriggers when the data of a casting has been updated.
Trigger
Updated ContactTriggers when the data of a contact has been updated in your Casting42 database.
Trigger
Updated TalentTriggers 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.
Action
Add File to TalentUploads a file such as a resume or PDF document to a talent's profile.
Action
Add Mediafile to TalentUploads a video or audio media file to a talent's profile in Casting42.
Action
Add Talent to GroupAdds one or more talents to an existing Casting42 group.
Action
Create CastingCreates a new casting project in Casting42 and returns it along with its talent sign-up link.
Action
Create ContactCreates a new contact in Casting42 with name, email, company, phone, language and address.
Action
Create GroupCreates a new group in Casting42 for organizing talents.
Action
Create or Update CandidateAdds a talent to a casting as a candidate, or updates the candidate's tags if the talent is already in that casting.
Action
Create TalentCreates a new talent profile in your Casting42 database and returns the created talent.
Action
Find CastingFinds a casting by its tag and returns the full casting record.
Action
Find Group by NameFinds a Casting42 group by its name.
Action
Get ContactReturns a single Casting42 contact identified by its tag.
Action
Get GroupReturns a Casting42 group and its talents by the group's tag.
Action
Get TalentReturns a single talent record, including custom fields and skills, by its tag.
Action
Update CastingUpdates an existing casting in Casting42, such as its name, description, dates, locations and sharing options. Fields left blank are not changed.
Action
Update ContactUpdates an existing contact in Casting42. Only the fields you fill in are changed.
Action
Update TalentUpdates an existing talent in Casting42, identified by its tag. Fields left blank keep their current values.
Trigger
Issue ClosedTriggers when an issue in a repository is closed.
Trigger
New BranchTriggers when a new branch is created in a GitHub repository.
Trigger
New CollaboratorTriggers when a new collaborator is added to a GitHub repository.
Trigger
New CommitTriggers when a new commit is pushed to a GitHub repository's default branch.
Trigger
New Commit CommentTriggers when someone comments on a commit in a repository.
Trigger
New GistTriggers when you create a new gist on GitHub.
Trigger
New Global EventTriggers when a new public event happens anywhere on GitHub, such as a push, fork, or new issue.
Trigger
New IssueTriggers when a new issue is created in a repository.
Trigger
New LabelTriggers when a new label is added to a GitHub repository.
Trigger
New MilestoneTriggers when a new milestone is created in a repository.
Trigger
New Pull RequestTriggers when a new pull request is opened in a repository.
Trigger
New ReleaseTriggers when a new release is published in a GitHub repository.
Trigger
New Repo EventTriggers when new activity (pushes, issues, pull requests, releases and more) happens in a GitHub repository.
Trigger
New RepositoryTriggers when a new public repository appears under a GitHub user or organization.
Trigger
New WatcherTriggers when someone starts watching a repository.
Action
Add Labels to IssueAdds labels to an issue or pull request in a GitHub repository, keeping its existing labels.
Action
Check Organization MembershipChecks whether a GitHub user is a member of an organization and returns true or false.
Action
Create BranchCreates a new branch in a repository, starting from the commit you choose.
Action
Create CommentAdds a comment to an issue or pull request in a GitHub repository.
Action
Create GistCreates a new gist with one file on the connected GitHub account.
Action
Create IssueCreates a new issue in a GitHub repository.
Action
Create or Update FileCreates a new file in a repository, or replaces an existing file's contents, as a commit.
Action
Create Pull RequestOpens a pull request asking to merge one branch into another.
Action
Delete BranchDeletes a branch from a repository. Any open pull request from that branch is closed.
Action
Find BranchFinds a branch in a GitHub repository by name and returns its latest commit and protection status.
Action
Find IssueFinds an issue in a GitHub repository by its number and returns its title, body, state, author and labels.
Action
Find OrganizationFinds a GitHub organization by its login and returns its profile details.
Action
Find Pull RequestFinds a pull request in a GitHub repository by its number and returns its title, state, branches and merge status.
Action
Find RepositoryReturns a GitHub repository by its owner and name, including its description, visibility, default branch and counts.
Action
Find UserFinds a GitHub user by username and returns their public profile.
Action
Get File ContentsReturns a file from a GitHub repository, with its base64-encoded content, at the default branch or a chosen branch, tag or commit.
Action
Submit ReviewSubmits a review on a pull request: approve it, request changes, or leave a review comment.
Action
Update IssueUpdates an existing issue in a GitHub repository, such as its title, text, state, labels or assignees.
Action
Update Pull RequestChanges a pull request's title, description, target branch, or open/closed state.
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 GitHub
ActiveCampaign to GitHubActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to GitHubOrganize anything with Airtable, a modern database created for everyone.
Asana to GitHubAsana is a collaborative information manager for workspace.
ClickUp to GitHubClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Discord to GitHubDiscord is an all-in-one voice and text chat for gamers.
Freshdesk to GitHubFreshdesk is a cloud-based customer support and helpdesk platform.
Questions
Casting42 and GitHub, 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 GitHub when something happens in Casting42?
Any of GitHub's 19 actions, including Create Branch, Create Comment, Create Gist and Create Issue. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from GitHub to Casting42?
Yes. When something happens in GitHub, your agent can act in Casting42 too. This page covers both directions: GitHub's triggers and Casting42's actions are listed here as well.
Do I have to build a connector for Casting42 or GitHub?
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.