Integration
Connect CryptAPI and openHandwerk
When Payment received (instant) fires in CryptAPI, your agent runs Update Customer in openHandwerk, or New Appointment in openHandwerk to Create payment address in CryptAPI. 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 CryptAPI and openHandwerk 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 CryptAPI and openHandwerk can do together
From CryptAPI to openHandwerk
When Payment received (instant) in CryptAPI
then Update Customer in openHandwerk
When Payment received (instant) in CryptAPI
then Get Customer in openHandwerk
From openHandwerk to CryptAPI
When New Appointment in openHandwerk
then Create payment address in CryptAPI
When New Calendar Category in openHandwerk
then Generate payment QR code in CryptAPI
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 CryptAPI and openHandwerk
Triggers and actions 5 triggers · 32 actions
Trigger
Payment received (instant)Fires when a payment address created via Create payment address receives funds; CryptAPI calls the callback URL supplied at creation time with the payment details.
Action
Convert priceConvert a value between a fiat currency and a cryptocurrency, or between two cryptocurrencies, for a given ticker.
Action
Create payment addressGenerate a new cryptocurrency payment address for a given ticker (e.g. btc, eth, trc20/usdt) that a customer can send funds to, with a callback URL for payment notifications.
Action
Estimate blockchain feesEstimate the blockchain network fee to forward a transaction to a wallet address, for a given cryptocurrency ticker.
Action
Generate payment QR codeGenerate a base64-encoded QR code image for a payment address, for a given cryptocurrency ticker.
Action
Get payment address logsGet the callback/payment activity log for a previously created payment address, for a given ticker.
Action
Get ticker infoGet details (minimum transaction amount, fees, current price) for a specific cryptocurrency ticker.
Action
List supported cryptocurrenciesList all cryptocurrencies and blockchains supported by CryptAPI, with logos, minimum transaction amounts, and fee tiers.
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.
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 CryptAPI
CryptAPI to RD StationRD Station is a complete digital marketing platform to help you generate more results in traffic generation...
CryptAPI to SLFSLF is a German-language geographic reference service covering cities, countries, and rivers.
CryptAPI to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
CryptAPI to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
CryptAPI to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
CryptAPI to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
More into openHandwerk
HubSpot to openHandwerkHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to openHandwerkGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to openHandwerkGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to openHandwerkGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to openHandwerkGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to openHandwerkMailchimp marketing automation and email platform.
Questions
CryptAPI and openHandwerk, answered
What can start an automation from CryptAPI?
Any of CryptAPI's 1 trigger in the catalog, including Payment received (instant). Describe the moment in plain language and your agent picks the right one.
What can your agent do in openHandwerk when something happens in CryptAPI?
Any of openHandwerk's 25 actions, including Create Appointment, Create Project, Update Appointment and Update Customer. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from openHandwerk to CryptAPI?
Yes. When something happens in openHandwerk, your agent can act in CryptAPI too. This page covers both directions: openHandwerk's triggers and CryptAPI's actions are listed here as well.
Do I have to build a connector for CryptAPI or openHandwerk?
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 CryptAPI and openHandwerk 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.