Integration
Connect Casting42 to Qstash
When New Casting fires in Casting42, your agent runs Batch publish messages in Qstash. 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 Qstash 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 Qstash
When New Casting in Casting42
then Batch publish messages in Qstash
When New Contact in Casting42
then Enqueue message in Qstash
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 Qstash
Triggers and actions 6 triggers · 36 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.
Action
Add queueCreate or update a queue (upsert), setting parallelism.
Action
Add scheduleCreate a cron-based schedule that periodically publishes a message to a destination.
Action
Add URL group endpointCreate a URL group or add/update an endpoint within it (fan-out publishing target).
Action
Batch publish messagesPublish multiple messages to multiple destinations in one call.
Action
Delete DLQ messageRemove a message from the dead-letter queue.
Action
Delete messageCancel a message that has not yet been delivered.
Action
Delete queueDelete a queue by name.
Action
Delete scheduleDelete a schedule by id.
Action
Delete URL groupDeletes a QStash URL group and all its endpoints. In-flight messages are not removed.
Action
Enqueue messageAdd a message to a named queue for sequential delivery.
Action
Get DLQ messageRetrieve a single dead-letter queue message by id.
Action
Get messageRetrieve a queued/published message by id.
Action
Get queueRetrieve a queue's configuration and stats by name.
Action
Get scheduleRetrieve a schedule by id.
Action
Get URL groupRetrieve a URL group and its endpoints by name.
Action
List DLQ messagesList messages that failed delivery and landed in the dead-letter queue.
Action
List queuesList all queues for the account.
Action
Publish messagePublish a single message to a URL or URL group for QStash to deliver.
Action
Retry DLQ messageRe-attempt delivery of a dead-lettered message now.
Action
Update scheduleUpdates an existing QStash schedule by replacing its settings (destination, cron, message and delivery options).
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 Qstash
HubSpot to QstashHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to QstashSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to QstashSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to QstashGoogle Sheets
Gmail to QstashGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to QstashGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Casting42 and Qstash, 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 Qstash when something happens in Casting42?
Any of Qstash's 20 actions, including Update schedule, Add queue, Add schedule and Add URL group endpoint. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Qstash to Casting42?
Qstash has no triggers in the catalog today, so automations start in Casting42. If you need the other direction, ask: your agent reads Qstash's API documentation and adds it.
Do I have to build a connector for Casting42 or Qstash?
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.