Integration
Connect DevCycle to Workato Api Proxy
When New Feature Created fires in DevCycle, your agent runs Update recipe in Workato Api Proxy. 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 DevCycle and Workato Api Proxy 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 DevCycle can start in Workato Api Proxy
When New Feature Created in DevCycle
then Update recipe in Workato Api Proxy
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 DevCycle and Workato Api Proxy
Triggers and actions 1 trigger · 17 actions
- New Feature Created
Triggers when a new feature is created in a DevCycle project.
- Add feature
Creates a new feature flag in a DevCycle project, with optional variations, variables and per-environment targeting.
- Add project
Creates a new project in your DevCycle organization.
- Add variable
Creates a new variable in a DevCycle project, optionally attached to a feature.
- Delete feature
Deletes a DevCycle feature from a project, optionally deleting its associated variables too.
- Get feature
Returns a DevCycle feature, including its variations, variables and environment targeting configurations.
- List environments
Returns the environments (development, staging, production, etc.) in a DevCycle project, including their keys and SDK keys.
- List features
Returns the features in a DevCycle project, optionally filtered by type, status, staleness, keys or a search term.
- List projects
Returns the DevCycle projects the connected account has permission to view.
- List variables
Returns the variables in a DevCycle project, optionally filtered by feature, type, status or search text.
- Update EdgeDB
Turns EdgeDB on or off for a DevCycle project and returns the updated project.
- Update feature
Updates an existing feature in a DevCycle project, such as its name, description, type, tags, variations, variables or environment targeting.
- Update variable
Updates an existing variable in a DevCycle project, such as its name, description, type, tags or key.
- Get job
Returns one job run of a recipe, including its status, timing, error details and the input and output of each step.
- Get recipe
Returns the details of a Workato recipe, including its name, status, connections and step definitions.
- List jobs
Returns the jobs run by a recipe, up to 1,000 at a time, along with succeeded and failed job counts.
- Start recipe
Starts a stopped Workato recipe so it begins processing trigger events.
- Update recipe
Updates an existing stopped recipe's name, steps, connections, folder or description. Running recipes cannot be updated.
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 DevCycle
DevCycle to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DevCycle to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
DevCycle to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
DevCycle to Google SheetsGoogle Sheets
DevCycle to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
DevCycle to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Workato Api Proxy
Questions
DevCycle and Workato Api Proxy, answered
What can start an automation from DevCycle?
Any of DevCycle's 1 trigger in the catalog, including New Feature Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Workato Api Proxy when something happens in DevCycle?
Any of Workato Api Proxy's 5 actions, including Update recipe, Get job, Get recipe and List jobs. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Workato Api Proxy to DevCycle?
Workato Api Proxy has no triggers in the catalog today, so automations start in DevCycle. If you need the other direction, ask: your agent reads Workato Api Proxy's API documentation and adds it.
Do I have to build a connector for DevCycle or Workato Api Proxy?
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 DevCycle and Workato Api Proxy 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.