Integration
Connect MOCO to Journy Io
When New Client fires in MOCO, your agent runs Add or update user in Journy Io. 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 MOCO and Journy Io 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 MOCO can start in Journy Io
When New Client in MOCO
then Add or update user in Journy Io
When New Company in MOCO
then Add users to account in Journy Io
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 MOCO and Journy Io
Triggers and actions 26 triggers · 31 actions
Trigger
New ClientTriggers when a new client is created.
Trigger
New CompanyTriggers when a new company is created.
Trigger
New ExpenseTriggers when an expense is created.
Trigger
New Exported Invoice (Bookkeeping)Triggers when a new invoice is exported (for the bookkeeping).
Trigger
New Incoming PaymentTriggers when a new incoming payment is created.
Trigger
New InvoiceTriggers when a new invoice is created.
Trigger
New Invoice StatusTriggers when the status of an invoice is changed.
Trigger
New OfferTriggers when a new offer is created.
Trigger
New Outgoing PaymentTriggers when a new outgoing payment is created.
Trigger
New Planning EntryTriggers when a new Planning Entry is created.
Trigger
New PresenceTriggers when a new Presence is created.
Trigger
New Project AssignmentTriggers when a person is assigned to a project.
Trigger
New PurchaseTriggers when a new purchase is created.
Trigger
New Recurred ExpenseTriggers when an expense is recurred.
Trigger
New TaskTriggers when a new task is created.
Trigger
New Time EntryTriggers when a new time entry is created.
Trigger
Unarchived ProjectTriggers when a project is made active again.
Trigger
Updated CompanyTriggers when a company was updated.
Trigger
Updated ExpenseTriggers when an expense was updated.
Trigger
Updated InvoiceTriggers when an invoice was updated.
Trigger
Updated LeadTriggers when a lead was updated.
Trigger
Updated Planning EntryTriggers when a Planning Entry was updated.
Trigger
Updated PresenceTriggers when a Presence was updated.
Trigger
Updated ProjectTriggers when a project was updated.
Trigger
Updated PurchaseTriggers when a purchase was updated.
Trigger
Updated Time EntryTriggers when a time entry was updated.
Action
Create CommentCreates a new Comment.
Action
Create CompanyCreates a new company (customer only).
Action
Create ContactCreates a new contact person.
Action
Create ExpenseCreates a new Expense.
Action
Create Incoming PaymentCreates a new incoming payment.
Action
Create LeadCreates a new lead.
Action
Create Outgoing PaymentCreates a new outgoing payment.
Action
Create ProjectCreates a new Project.
Action
Create PurchaseCreates a new Purchase.
Action
Create TaskCreates a new project task.
Action
Create Time EntryCreate a new time entry.
Action
Find CompanyFinds an existing Company.
Action
Find ContactFinds an existing Contact.
Action
Find ExpenseFinds an existing Expense.
Action
Find InvoiceFinds an existing Invoice.
Action
Find LeadFinds an existing lead.
Action
Find OfferFinds an existing Offer.
Action
Find Planning EntryFinds an existing Planning Entry.
Action
Find ProjectFinds an existing project.
Action
Find PurchaseFinds an existing Purchase.
Action
Find TaskFinds an active Task for a Project.
Action
Find Time EntryFinds an existing Time Entry.
Action
Find UserFinds an existing active user.
Action
Record PresenceRecord a new presence.
Action
Add or update accountCreates an account in journy.io, or updates its properties if it already exists.
Action
Add or update userCreates a user in journy.io, or updates the properties of an existing user identified by user ID or email.
Action
Add users to accountAdds up to 100 users to a journy.io account, identifying the account by its ID or domain.
Action
Delete accountDeletes an account in journy.io, identified by its account ID and/or domain.
Action
Delete userDeletes a user from journy.io, identified by user ID, email, or both.
Action
List eventsReturns the event types defined in your journy.io workspace, with each event's name, id and group.
Action
Remove user from accountRemoves up to 100 users from a journy.io account. The users stay stored in journy.io but are marked as removed from the account.
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 MOCO
MOCO to ip-apiip-api resolves an IP address or domain name to a physical location.
MOCO to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
MOCO to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
MOCO to StripeStripe is a payment processing platform for online businesses.
MOCO to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
MOCO to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Journy Io
HubSpot to Journy IoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Journy IoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Journy IoSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Journy IoGoogle Sheets
Gmail to Journy IoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Journy IoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
MOCO and Journy Io, answered
What can start an automation from MOCO?
Any of MOCO's 26 triggers in the catalog, including New Client, New Company, New Expense and New Exported Invoice (Bookkeeping). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Journy Io when something happens in MOCO?
Any of Journy Io's 7 actions, including Add or update account, Add or update user, Add users to account and List events. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Journy Io to MOCO?
Journy Io has no triggers in the catalog today, so automations start in MOCO. If you need the other direction, ask: your agent reads Journy Io's API documentation and adds it.
Do I have to build a connector for MOCO or Journy Io?
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 MOCO and Journy Io 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.