Integration
Connect Amberscript to Fly.io Machines API
When Job Finished fires in Amberscript, your agent runs Create App in Fly.io Machines API. 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 Amberscript and Fly.io Machines API 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 Amberscript can start in Fly.io Machines API
When Job Finished in Amberscript
then Create App in Fly.io Machines API
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 Amberscript and Fly.io Machines API
Triggers and actions 1 trigger · 20 actions
- Job Finished
Triggers when a job has finished on our platform.
- Add glossary
Create a new glossary of terms that can be referenced by glossaryId on job upload for improved transcription accuracy.
- Create New Job
This action creates a new job on the Amberscript platform.
- Delete glossary
Delete an existing glossary.
- Delete job
Delete a transcription job.
- Get job
Retrieve the status/details of a transcription job.
- Get job transcript
Download a finished job's transcript/subtitles in a chosen export format.
- List glossaries
List all glossaries defined on the account (used to supply glossaryId when uploading a job).
- List jobs
List all transcription jobs for the account.
- Update glossary
Update an existing glossary's terms.
- Create App
Creates a new Fly.io app in the chosen organization and returns its id.
- Create Machine
Creates a new Machine in a Fly.io app from the image and configuration you provide, and returns the created Machine.
- Create Volume
Creates a persistent storage volume for a Fly.io app in the chosen region.
- Delete App
Deletes a Fly.io app by its name.
- Delete Machine
Deletes a Machine from a Fly.io app, optionally force-killing it if it is still running.
- Delete Volume
Destroys a volume in a Fly.io app and returns the deleted volume's details.
- Extend Volume
Extends a Fly.io volume to a larger size in gigabytes. Returns the updated volume and whether its Machine needs a restart.
- Start Machine
Starts a stopped or suspended Machine in a Fly.io app.
- Stop Machine
Stops a running Fly.io Machine in an app, optionally choosing the stop signal and how long to wait before it is killed.
- Suspend Machine
Suspends a Machine in a Fly.io app so its next start can resume from a snapshot instead of a cold boot.
- Update Machine
Updates a Fly.io Machine's configuration, such as its image, guest size, environment variables, services or restart policy, and returns the updated Machine.
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 Amberscript
Amberscript to OntraportOntraport is an all-in-one CRM, marketing automation, and e-commerce platform.
Amberscript to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Amberscript to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Amberscript to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Amberscript to Google SheetsGoogle Sheets
Amberscript to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
More into Fly.io Machines API
Google Calendar to Fly.io Machines APIGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Amberscript and Fly.io Machines API, answered
What can start an automation from Amberscript?
Any of Amberscript's 1 trigger in the catalog, including Job Finished. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Fly.io Machines API when something happens in Amberscript?
Any of Fly.io Machines API's 11 actions, including Create App, Create Machine, Create Volume and Update Machine. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Fly.io Machines API to Amberscript?
Fly.io Machines API has no triggers in the catalog today, so automations start in Amberscript. If you need the other direction, ask: your agent reads Fly.io Machines API's API documentation and adds it.
Do I have to build a connector for Amberscript or Fly.io Machines API?
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.