Integration
Connect JOIN and modular365
When Application Created fires in JOIN, your agent runs Update Multiple Records in modular365, or New Record in modular365 to Add candidate note in JOIN. 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 modular365 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 JOIN and modular365 can do together
From JOIN to modular365
When Application Created in JOIN
then Update Multiple Records in modular365
When Job Published in JOIN
then Update Record in modular365
From modular365 to JOIN
When New Record in modular365
then Add candidate note in JOIN
When New Record in modular365
then Add job in JOIN
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 modular365
Triggers and actions 4 triggers · 24 actions
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
Delete candidatePermanently deletes a candidate together with their applications, notes and attachments.
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 one published JOIN job by ID, including its hiring stages and their IDs.
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
Move application to stageMoves an application to another hiring stage of its job.
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.
Trigger
New RecordTriggers when a new record is added to a Modular 365 table, such as a new customer or work order.
Action
Find RecordsReturns records from a Modular 365 table, optionally narrowed by a filter, one page at a time.
Action
Insert RecordCreates a new record in a Modular 365 table, such as a customer or work order. The record ID is generated by Modular 365.
Action
List Table FieldsReturns the fields of a Modular 365 table, with their internal names, display labels and form order.
Action
List TablesReturns the tables in your Modular 365 company with their display names in the chosen language.
Action
Update Multiple RecordsUpdates every record in a Modular 365 table that matches your filters. Use with care: broad filters change many records at once.
Action
Update RecordUpdates exactly one record in a Modular 365 table that matches your filters. Fails safely if no record or more than one record matches.
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 modular365
HubSpot to modular365HubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to modular365Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to modular365Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to modular365Google Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to modular365Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to modular365Mailchimp marketing automation and email platform.
Questions
JOIN and modular365, 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 modular365 when something happens in JOIN?
Any of modular365's 6 actions, including Update Multiple Records, Update Record, Find Records and Insert Record. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from modular365 to JOIN?
Yes. When something happens in modular365, your agent can act in JOIN too. This page covers both directions: modular365's triggers and JOIN's actions are listed here as well.
Do I have to build a connector for JOIN or modular365?
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 modular365 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.