Integration
Connect JOIN to RD Station
When Application Created fires in JOIN, your agent runs Add tag to contact in RD Station. 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 JOIN and RD Station 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 JOIN can start in RD Station
When Application Created in JOIN
then Add tag to contact in RD Station
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 JOIN and RD Station
Triggers and actions 3 triggers · 30 actions
- Application Created
Triggers when a new job application is received in JOIN.
- Job Published
Triggers when a job is published (goes online) in JOIN.
- Job Unpublished
Triggers when a job is taken offline or archived in JOIN.
- Add candidate note
Adds a note to a candidate in JOIN.
- Add job
Creates a job in JOIN. New jobs are activated and multiposted to job boards automatically.
- Add location
Creates a new office location in JOIN that job ads can be assigned to.
- Create Application
Creates an application for a candidate on a JOIN job, optionally attaching documents such as a CV.
- Get application
Returns one job application, including its candidate, job, attachments, screening answers and pipeline stage.
- Get candidate
Returns a single JOIN candidate by id, including contact details, tags, consent status and their applications, with notes optionally embedded.
- Get job
Returns a single JOIN job by its ID, including its title, status, office and optionally its full content.
- Get Jobs
Returns jobs in your JOIN account, optionally filtered by status, title, country, external id, or creation/update dates.
- Get Online Jobs
Returns the jobs currently published (online) in your JOIN account, optionally filtered by title, country, dates or external id.
- List applications
Returns the applications in your JOIN account, optionally filtered by job, dates, country, hiring state or pipeline stage.
- List candidate notes
Returns all notes recorded on a candidate in JOIN, including replies.
- List candidates
Returns the candidates in your JOIN company, optionally filtered by a name/email search or creation date.
- List candidate scorecards
Returns the scorecards submitted for a candidate's job application, including each interviewer's overall recommendation, attribute ratings and question answers.
- List locations
Returns the office locations in your JOIN account, optionally filtered by country or city.
- Update job
Updates an existing job's details, such as title, description, office, salary, and application requirements. Fields you leave blank stay unchanged.
- Update Job Status
Changes a JOIN job's status to online, offline or archived, and returns the job's ID.
- Add custom field
Creates a new custom contact field in your RD Station Marketing account.
- Add tag to contact
Adds one or more tags to an existing RD Station Marketing contact, found by UUID, email or phone. Tags are added alongside the contact's existing tags.
- Conversion Event
Records a conversion event in RD Station Marketing, creating or updating the contact identified by email or phone.
- Delete contact
Deletes a contact from RD Station Marketing, found by its UUID, email or phone.
- Delete custom field
Deletes a custom contact field from the RD Station Marketing account. Default fields cannot be deleted.
- Get contact
Returns a contact's standard and custom fields, looked up by UUID, email or phone.
- List contact events
Returns the conversion or opportunity events recorded for an RD Station Marketing contact.
- List custom fields
Returns all contact fields in the RD Station Marketing account, both standard and custom fields.
- List segmentation contacts
Returns the contacts that belong to an RD Station Marketing segmentation.
- List segmentations
Returns the segmentations (contact segments) defined in your RD Station Marketing account.
- Lost Deal
Marks an existing RD Station Marketing contact as a lost opportunity in the default funnel, with a loss reason.
- Update contact
Updates an existing contact in RD Station Marketing, found by its uuid, email or phone. Creates the contact if none matches.
- Update custom field
Updates the name, label, data type, presentation type and options of an existing contact custom field in RD Station Marketing.
- Won Deal
Marks an existing RD Station Marketing contact as a won opportunity (sale), optionally with the deal value.
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 JOIN
JOIN to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
JOIN to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
JOIN to MailchimpMailchimp marketing automation and email platform.
JOIN to StripeStripe is a payment processing platform for online businesses.
JOIN to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
JOIN to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into RD Station
CryptAPI to RD StationCryptAPI is a non-custodial cryptocurrency payment processor that generates payment addresses and forwards...
HubSpot to RD StationHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to RD StationGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to RD StationGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
JOIN and RD Station, answered
What can start an automation from JOIN?
Any of JOIN's 3 triggers in the catalog, including Application Created, Job Published and Job Unpublished. Describe the moment in plain language and your agent picks the right one.
What can your agent do in RD Station when something happens in JOIN?
Any of RD Station's 14 actions, including Update contact, Update custom field, Add custom field and Add tag to contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from RD Station to JOIN?
RD Station has no triggers in the catalog today, so automations start in JOIN. If you need the other direction, ask: your agent reads RD Station's API documentation and adds it.
Do I have to build a connector for JOIN or RD Station?
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 JOIN and RD Station 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.