Integration
Connect Auphonic to Workato Api Proxy
When New Production fires in Auphonic, 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 Auphonic and Workato Api Proxy 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 Auphonic can start in Workato Api Proxy
When New Production in Auphonic
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 Auphonic and Workato Api Proxy
Triggers and actions 1 trigger · 18 actions
- New Production
Fires when a production created from the chosen preset finishes processing (Done or Error).
- Add production using simple API
Creates a singletrack Auphonic production in one request: sets the input audio, metadata and audio processing options, optionally based on a preset, and optionally starts processing right away.
- Create Preset
Creates a new Auphonic preset with the given name and returns its UUID.
- Create Production
Creates a new Auphonic audio production, optionally from a preset, with metadata, output files, algorithms, chapters and outgoing services, and optionally starts processing right away.
- Delete production
Delete a production.
- Get preset
Get the full details of one Auphonic preset: name, audio algorithms, output files, outgoing services, metadata and more.
- Get production
Returns the full details of one Auphonic production: status, metadata, algorithms, output files, outgoing services, chapters and audio statistics.
- Get production status
Returns the current processing status code and status text of an Auphonic production.
- Get user
Returns the account information and notification settings of the connected Auphonic user, including available credits.
- List productions
Lists the productions in the connected Auphonic account, newest first.
- Start production
Starts audio post production processing for an existing Auphonic production.
- Stop production
Stops a production that is currently processing in Auphonic.
- Update production
Update a production.
- Upload production file
Uploads an audio/video file and/or a cover image to an existing Auphonic production.
- 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 Auphonic
Auphonic to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Auphonic to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Auphonic to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Auphonic to Google SheetsGoogle Sheets
Auphonic to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Auphonic to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Workato Api Proxy
Questions
Auphonic and Workato Api Proxy, answered
What can start an automation from Auphonic?
Any of Auphonic's 1 trigger in the catalog, including New Production. 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 Auphonic?
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 Auphonic?
Workato Api Proxy has no triggers in the catalog today, so automations start in Auphonic. 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 Auphonic 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.
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.