Integration
Connect Noko and Onepay
When Entry Changed fires in Noko, your agent runs Create Customer Card Request in Onepay, or New Customer in Onepay to Mark Invoice as Paid in Noko. 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 Noko and Onepay 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 Noko and Onepay can do together
From Noko to Onepay
When Entry Changed in Noko
then Create Customer Card Request in Onepay
When Invoice Changed in Noko
then Get Customer in Onepay
From Onepay to Noko
When New Customer in Onepay
then Mark Invoice as Paid in Noko
When New Customer in Onepay
then Create Project in Noko
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 Noko and Onepay
Triggers and actions 7 triggers · 33 actions
Trigger
Entry ChangedTriggers when a Noko time entry is created or changed.
Trigger
Invoice ChangedTriggers when a Noko invoice is created or changed.
Trigger
New EntryTriggers when a new time entry is logged in Noko.
Trigger
New ExpenseTriggers when a new expense is logged in Noko.
Trigger
New InvoiceTriggers when a new invoice is created in Noko.
Trigger
New ProjectTriggers when a new project is created in Noko.
Action
Approve EntryMarks a Noko time entry as approved.
Action
Archive ProjectArchives a Noko project.
Action
Create EntryLogs a new time entry in Noko.
Action
Create ExpenseLogs a new expense against a Noko project.
Action
Create ProjectCreates a new Noko project.
Action
Create TagsCreates one or more Noko tags.
Action
Delete EntryDeletes a Noko time entry.
Action
Find ExpenseFinds the most recent Noko expense matching the filters.
Action
Find InvoiceFinds a Noko invoice by reference, state or company.
Action
Find ProjectFinds a Noko project by name.
Action
Find UserFinds a Noko user by name or email.
Action
Get EntryReturns a single Noko time entry by its ID.
Action
Mark Invoice as PaidMarks a Noko invoice as paid.
Action
Update EntryUpdates a Noko time entry's date, minutes, description, project or user.
Trigger
New CustomerTriggers when a new customer is added to your Onepay app.
Action
Create Customer Card RequestCreates an Onepay customer (or reuses an existing one by Customer ID) and returns a secure link where they enter a card to save.
Action
Create ItemCreates a product or service line item you can attach to Onepay payments.
Action
Delete Customer CardPermanently deactivates a customer's saved card so it can no longer be charged.
Action
Delete ItemPermanently deletes an Onepay item that is not used by completed transactions.
Action
Delete Payment LinkDeactivates a payment link that has no successful payments.
Action
Get CustomerReturns a customer with their saved cards and transaction history.
Action
Get Customer CardReturns one of a customer's saved cards.
Action
Get Payment LinkReturns a payment link, including whether the customer has paid it.
Action
Get Payout TransactionReturns the settlement breakdown of a transaction: amount, commission, net payout and settlement date.
Action
Get Transaction StatusReturns whether an Onepay transaction was paid, with its amount and payment time.
Action
List Customer CardsReturns a customer's saved card tokens.
Action
List CustomersReturns all customers saved in your Onepay app.
Action
List Customer TransactionsReturns a customer's charge history, newest first.
Action
List ItemsReturns all items created under your Onepay App ID.
Action
List Payout TransactionsReturns settlement transactions in a date range, one page at a time.
Action
Make PaymentCharges a customer's saved card for any amount, with no action needed from the customer.
Action
Refund TransactionStarts a full or partial refund of a paid live Onepay transaction.
Action
Update ItemUpdates the fields you supply on an existing Onepay item; others keep their values.
Action
Update Payment Link DescriptionChanges the description of a payment link (the only field Onepay lets you change after creation).
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 Noko
Noko to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Noko to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Noko to StripeStripe is a payment processing platform for online businesses.
Noko to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Noko to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Noko to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Onepay
HubSpot to OnepayHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to OnepayGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to OnepayGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to OnepayGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to OnepayGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to OnepayMailchimp marketing automation and email platform.
Questions
Noko and Onepay, answered
What can start an automation from Noko?
Any of Noko's 6 triggers in the catalog, including Entry Changed, Invoice Changed, New Entry and New Expense. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Onepay when something happens in Noko?
Any of Onepay's 19 actions, including Create Customer Card Request, Create Item, Update Item and Update Payment Link Description. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Onepay to Noko?
Yes. When something happens in Onepay, your agent can act in Noko too. This page covers both directions: Onepay's triggers and Noko's actions are listed here as well.
Do I have to build a connector for Noko or Onepay?
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 Noko and Onepay 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.