Integration
Connect openHandwerk to Fly.io Machines API
When New Appointment fires in openHandwerk, 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 openHandwerk and Fly.io Machines API 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 openHandwerk can start in Fly.io Machines API
When New Appointment in openHandwerk
then Create App in Fly.io Machines API
When New Calendar Category in openHandwerk
then Create Machine 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 openHandwerk and Fly.io Machines API
Triggers and actions 4 triggers · 36 actions
Trigger
New AppointmentTriggers when a new appointment is created.
Trigger
New Calendar CategoryTriggers when a new calendar category is created.
Trigger
New CustomerTriggers when a new customer is created.
Trigger
New ProjectTriggers when a new order project is created.
Action
Create AppointmentCreates a calendar appointment, optionally linked to a project and with employee attendees.
Action
Create ProjectCreates a new project for a customer.
Action
Delete ProductDeletes a product.
Action
Delete SupplierDeletes a supplier.
Action
Get AppointmentReturns one appointment by its ID.
Action
Get CustomerReturns one customer by its ID.
Action
Get EmployeeReturns one employee by its ID.
Action
Get OfferReturns one offer by its ID.
Action
Get OrderReturns one order by its ID.
Action
Get ProductReturns one product by its ID.
Action
Get SupplierReturns one supplier by its ID.
Action
List AppointmentsReturns appointments, optionally filtered by title, attendee email, project or category.
Action
List Calendar CategoriesReturns the appointment calendar categories.
Action
List CustomersReturns customers, optionally filtered by company, city, email and other fields.
Action
List EmployeesReturns the account's employees, optionally filtered by name or role.
Action
List OffersReturns offers (quotes).
Action
List OrdersReturns orders (projects of type order).
Action
List ProductsReturns all products.
Action
List SuppliersReturns all suppliers.
Action
Search CustomersFinds customers matching a search term.
Action
Search ProjectsFinds a project matching a search term.
Action
Update AppointmentUpdates an existing calendar appointment.
Action
Update CustomerUpdates an existing customer.
Action
Update ProductUpdates an existing product.
Action
Update SupplierUpdates an existing supplier.
Action
Create AppCreates a new Fly.io app in the chosen organization and returns its id.
Action
Create MachineCreates a new Machine in a Fly.io app from the image and configuration you provide, and returns the created Machine.
Action
Create VolumeCreates a persistent storage volume for a Fly.io app in the chosen region.
Action
Delete AppDeletes a Fly.io app by its name.
Action
Delete MachineDeletes a Machine from a Fly.io app, optionally force-killing it if it is still running.
Action
Delete VolumeDestroys a volume in a Fly.io app and returns the deleted volume's details.
Action
Extend VolumeExtends a Fly.io volume to a larger size in gigabytes. Returns the updated volume and whether its Machine needs a restart.
Action
Start MachineStarts a stopped or suspended Machine in a Fly.io app.
Action
Stop MachineStops a running Fly.io Machine in an app, optionally choosing the stop signal and how long to wait before it is killed.
Action
Suspend MachineSuspends a Machine in a Fly.io app so its next start can resume from a snapshot instead of a cold boot.
Action
Update MachineUpdates 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 openHandwerk
openHandwerk to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
openHandwerk to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
openHandwerk to StripeStripe is a payment processing platform for online businesses.
openHandwerk to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
openHandwerk to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
openHandwerk to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Fly.io Machines API
HubSpot to Fly.io Machines APIHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Fly.io Machines APISalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Fly.io Machines APISlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Fly.io Machines APIGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Fly.io Machines APIGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Fly.io Machines APIGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
openHandwerk and Fly.io Machines API, answered
What can start an automation from openHandwerk?
Any of openHandwerk's 4 triggers in the catalog, including New Appointment, New Calendar Category, New Customer and New Project. 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 openHandwerk?
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 openHandwerk?
Fly.io Machines API has no triggers in the catalog today, so automations start in openHandwerk. 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 openHandwerk 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.
Can my AI client use openHandwerk and Fly.io Machines API 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.