Integration
Connect Noko and Skyvern
When Entry Changed fires in Noko, your agent runs Create and Run a Task in Skyvern, or New or Updated Skyvern Workflow in Skyvern 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 Skyvern 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 Skyvern can do together
From Noko to Skyvern
When Entry Changed in Noko
then Create and Run a Task in Skyvern
When Invoice Changed in Noko
then Create and Run Task V2 in Skyvern
From Skyvern to Noko
When New or Updated Skyvern Workflow in Skyvern
then Mark Invoice as Paid in Noko
When New or Updated Skyvern Workflow in Skyvern
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 Skyvern
Triggers and actions 7 triggers · 29 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 or Updated Skyvern WorkflowTriggers when a Skyvern workflow (agent) is created or a new version of it is saved.
Action
Add browser sessionCreates a Skyvern browser session that persists across multiple task and workflow runs, and returns its session id and live-view link.
Action
Add credentialCreates a new stored credential (login, credit card or secret) in your Skyvern organization for use by tasks and agents.
Action
Add workflowCreates a new Skyvern workflow (agent) from a JSON or YAML definition and returns the saved workflow.
Action
Cancel runCancels a running Skyvern task run or workflow run by its id.
Action
Create and Run a TaskStarts a Skyvern browser-automation task from a plain-language prompt and returns the new run, including its id, status and link in the Skyvern app.
Action
Create and Run Task V2Starts a Skyvern 2.0 browser task from a natural-language prompt and returns the new run's id and status.
Action
Delete workflowDeletes a Skyvern workflow (agent) by its ID.
Action
Get a Browser SessionReturns the details of a Skyvern browser session, including its status, browser address for connecting, downloaded files and recordings.
Action
Get a TaskReturns a Skyvern task run by its id, including its status, extracted output, downloaded files, recording and screenshots.
Action
Get a Task V2Returns the status, output, recording and screenshots of a Skyvern task run.
Action
Get a WorkflowReturns a Skyvern workflow (agent) by its permanent id, including its blocks, parameters and settings.
Action
List credentialsReturns the credentials stored in your Skyvern organization, optionally filtered by vault, type or search text. Secrets are never included.
Action
List runsReturns your organization's task and agent runs, newest first, optionally filtered by status, run type, agent, tags, failure category or a search term.
Action
List workflowsReturns the workflows (agents) in your Skyvern organization, optionally filtered by search text, folder, status or tags. Returns up to 100 workflows.
Action
Run a WorkflowStarts a run of one of your Skyvern workflows (agents) with the parameters you supply, and returns the new run's id, status and link.
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 Skyvern
HubSpot to SkyvernHubSpot is your all-in-one stop for all of your marketing software needs.
CentralStationCRM to SkyvernCentralStationCRM is an easy CRM software. We focus on ease of use, collaboration and work best when you...
Cliniko to SkyvernCliniko is a practice management platform — manage patients, appointments, invoices, contacts, and...
Salesforce to SkyvernSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to SkyvernGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to SkyvernGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Noko and Skyvern, 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 Skyvern when something happens in Noko?
Any of Skyvern's 15 actions, including Create and Run a Task, Create and Run Task V2, Add browser session and Add credential. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Skyvern to Noko?
Yes. When something happens in Skyvern, your agent can act in Noko too. This page covers both directions: Skyvern's triggers and Noko's actions are listed here as well.
Do I have to build a connector for Noko or Skyvern?
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 Skyvern 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.