Integration
Connect CryptAPI and JOIN
When Payment received (instant) fires in CryptAPI, your agent runs Add candidate note in JOIN, or Application Created in JOIN 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 JOIN 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 CryptAPI and JOIN can do together
From CryptAPI to JOIN
When Payment received (instant) in CryptAPI
then Add candidate note in JOIN
When Payment received (instant) in CryptAPI
then Add job in JOIN
From JOIN to CryptAPI
When Application Created in JOIN
then Create payment address in CryptAPI
When Job Published in JOIN
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 JOIN
Triggers and actions 4 triggers · 23 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
Application CreatedTriggers when a new job application is received in JOIN.
Trigger
Job PublishedTriggers when a job is published (goes online) in JOIN.
Trigger
Job UnpublishedTriggers when a job is taken offline or archived in JOIN.
Action
Add candidate noteAdds a note to a candidate in JOIN.
Action
Add jobCreates a job in JOIN. New jobs are activated and multiposted to job boards automatically.
Action
Add locationCreates a new office location in JOIN that job ads can be assigned to.
Action
Create ApplicationCreates an application for a candidate on a JOIN job, optionally attaching documents such as a CV.
Action
Get applicationReturns one job application, including its candidate, job, attachments, screening answers and pipeline stage.
Action
Get candidateReturns a single JOIN candidate by id, including contact details, tags, consent status and their applications, with notes optionally embedded.
Action
Get jobReturns a single JOIN job by its ID, including its title, status, office and optionally its full content.
Action
Get JobsReturns jobs in your JOIN account, optionally filtered by status, title, country, external id, or creation/update dates.
Action
Get Online JobsReturns the jobs currently published (online) in your JOIN account, optionally filtered by title, country, dates or external id.
Action
List applicationsReturns the applications in your JOIN account, optionally filtered by job, dates, country, hiring state or pipeline stage.
Action
List candidate notesReturns all notes recorded on a candidate in JOIN, including replies.
Action
List candidatesReturns the candidates in your JOIN company, optionally filtered by a name/email search or creation date.
Action
List candidate scorecardsReturns the scorecards submitted for a candidate's job application, including each interviewer's overall recommendation, attribute ratings and question answers.
Action
List locationsReturns the office locations in your JOIN account, optionally filtered by country or city.
Action
Update jobUpdates an existing job's details, such as title, description, office, salary, and application requirements. Fields you leave blank stay unchanged.
Action
Update Job StatusChanges a JOIN job's status to online, offline or archived, and returns the job's ID.
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 JOIN
HubSpot to JOINHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to JOINGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to JOINGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to JOINGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to JOINGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
ActiveCampaign to JOINActiveCampaign is a marketing automation, email marketing, and CRM platform.
Questions
CryptAPI and JOIN, 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 JOIN when something happens in CryptAPI?
Any of JOIN's 16 actions, including Create Application, Update job, Update Job Status and Add candidate note. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from JOIN to CryptAPI?
Yes. When something happens in JOIN, your agent can act in CryptAPI too. This page covers both directions: JOIN's triggers and CryptAPI's actions are listed here as well.
Do I have to build a connector for CryptAPI or JOIN?
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 JOIN 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.