Integration
Connect Noko and ProWorkflow Classic
When Entry Changed fires in Noko, your agent runs Add Contact in ProWorkflow Classic, or New Company in ProWorkflow Classic 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 ProWorkflow Classic 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 ProWorkflow Classic can do together
From Noko to ProWorkflow Classic
When Entry Changed in Noko
then Add Contact in ProWorkflow Classic
When Invoice Changed in Noko
then Add Project Task in ProWorkflow Classic
From ProWorkflow Classic to Noko
When New Company in ProWorkflow Classic
then Mark Invoice as Paid in Noko
When New Contact in ProWorkflow Classic
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 ProWorkflow Classic
Triggers and actions 11 triggers · 37 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 CompanyTriggers when a new company is added in ProWorkflow.
Trigger
New ContactTriggers when a new contact is added in ProWorkflow.
Trigger
New ProjectTriggers when a new project is added in ProWorkflow.
Trigger
New TaskTriggers when a new task is added to a ProWorkflow project.
Trigger
New TimeTriggers when a new time record is logged in ProWorkflow.
Action
Add Client to ProjectAdds a client contact to a project, keeping the project's existing contacts.
Action
Add CompanyCreates a company (client, contractor, staff or other) in ProWorkflow.
Action
Add ContactCreates a contact in ProWorkflow.
Action
Add ProjectCreates a client project in ProWorkflow.
Action
Add Project TaskCreates a task in a ProWorkflow project.
Action
Add TimeLogs a time record against a ProWorkflow task.
Action
Delete CompanyDeletes a company from ProWorkflow.
Action
Delete ContactDeletes a contact from ProWorkflow.
Action
Delete ProjectDeletes a project from ProWorkflow.
Action
Delete TaskDeletes a task from ProWorkflow.
Action
Find ClientFinds client companies in ProWorkflow matching a search term, name, code, email, tag or other filters, and returns the matching clients.
Action
Find CompanyReturns a ProWorkflow company by its ID.
Action
Find ContactReturns a ProWorkflow contact by its ID.
Action
Find ContractorFinds contractor companies in ProWorkflow matching a name, code, email or search term, and returns the matching companies.
Action
Find ProjectReturns a ProWorkflow project by its ID.
Action
Find StaffFinds staff contacts in ProWorkflow by name, email, search term or other filters and returns the matching staff members.
Action
Find TaskReturns a ProWorkflow task by its ID.
Action
Make Task ActiveSets a ProWorkflow task's status to active.
Action
Update CompanyUpdates an existing company's details in ProWorkflow.
Action
Update ContactUpdates an existing contact in ProWorkflow.
Action
Update Contact LocationUpdates the address (street, city, state, postal code and country) of an existing ProWorkflow contact.
Action
Update ProjectUpdates an existing project in ProWorkflow.
Action
Update TaskUpdates an existing task in ProWorkflow, including marking it active or complete.
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 ProWorkflow Classic
HubSpot to ProWorkflow ClassicHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to ProWorkflow ClassicGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to ProWorkflow ClassicGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ProWorkflow ClassicGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ProWorkflow ClassicGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to ProWorkflow ClassicMailchimp marketing automation and email platform.
Questions
Noko and ProWorkflow Classic, 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 ProWorkflow Classic when something happens in Noko?
Any of ProWorkflow Classic's 23 actions, including Update Company, Update Contact, Update Contact Location and Update Project. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from ProWorkflow Classic to Noko?
Yes. When something happens in ProWorkflow Classic, your agent can act in Noko too. This page covers both directions: ProWorkflow Classic's triggers and Noko's actions are listed here as well.
Do I have to build a connector for Noko or ProWorkflow Classic?
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 ProWorkflow Classic 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.