Integration
Connect Disco to Google Cloud Scheduler
When Pathway Added fires in Disco, your agent runs Create HTTP Job in Google Cloud Scheduler. 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 Disco and Google Cloud Scheduler 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 Disco can start in Google Cloud Scheduler
When Pathway Added in Disco
then Create HTTP Job in Google Cloud Scheduler
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 Disco and Google Cloud Scheduler
Triggers and actions 6 triggers · 21 actions
- Pathway Added
Triggers when a new pathway is created in your Disco academy.
- Pathway Updated
Triggers when a pathway is created or its details change in your Disco academy.
- Product Added
Triggers when a new Program (called Product in the API) is created in your Disco academy.
- Product Updated
Triggers when a Program is created or its details change in your Disco academy.
- User Joined Pathway
Triggers when a member joins the selected Disco pathway.
- User Joined Product
Triggers when a member joins the selected Disco Program.
- Activate a User
Reactivates a member who was deactivated in your Disco academy.
- Add User to a Pathway
Adds an existing member directly to a Disco pathway, skipping registration.
- Add User to a Product
Adds an existing member directly to a Disco Program, skipping registration.
- Add User to Community
Adds a member to your Disco academy, or returns the existing member with that email.
- Deactivate a User
Deactivates an active member in your Disco academy.
- Fetch a User Profile
Returns one member's profile by their Disco member ID.
- Get Login Link for User
Returns a magic login link for an existing Disco member.
- Invite User to a Pathway
Invites a person by email to a Disco pathway.
- Invite User to a Product
Invites a person by email to a Disco Program.
- Remove User From a Group
Removes a member from a Disco Member Group and its subgroups.
- Remove User From a Pathway
Unenrolls a member from a Disco pathway.
- Remove User From a Product
Unenrolls a member from a Disco Program.
- Remove User From Community
Removes a member and all their activity from your Disco academy.
- Create HTTP Job
Creates a Cloud Scheduler job that calls an HTTP URL on a cron schedule.
- Delete Job
Permanently deletes a Cloud Scheduler job.
- Get Job
Returns a Cloud Scheduler job's schedule, target and current state.
- List Jobs
Returns the Cloud Scheduler jobs in a project location.
- Pause Job
Pauses a Cloud Scheduler job so it stops running on its schedule until resumed.
- Resume Job
Resumes a paused Cloud Scheduler job so it runs on its schedule again.
- Run Job Now
Runs a Cloud Scheduler job immediately. The job must be enabled; a paused job has to be resumed first.
- Update Job
Changes a Cloud Scheduler HTTP job's schedule, time zone, URL, method or description. Fields left blank are not changed.
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 Disco
Disco to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Disco to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Disco to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Disco to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Disco to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Disco to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Google Cloud Scheduler
TidyHQ to Google Cloud SchedulerWhen your group needs to collect membership dues, communicate with everyone and keep track of your finances...
Questions
Disco and Google Cloud Scheduler, answered
What can start an automation from Disco?
Any of Disco's 6 triggers in the catalog, including Pathway Added, Pathway Updated, Product Added and Product Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Google Cloud Scheduler when something happens in Disco?
Any of Google Cloud Scheduler's 8 actions, including Create HTTP Job, Update Job, Get Job and List Jobs. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Google Cloud Scheduler to Disco?
Google Cloud Scheduler has no triggers in the catalog today, so automations start in Disco. If you need the other direction, ask: your agent reads Google Cloud Scheduler's API documentation and adds it.
Do I have to build a connector for Disco or Google Cloud Scheduler?
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 Disco and Google Cloud Scheduler without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app 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.