Noko Zapier integrationAutomate Noko with Zapier.
The Noko Zapier integration gives you 14 triggers, 3 actions and 3 searches. Every trigger is instant, so a new time entry, expense or invoice in Noko reaches your other tools straight away, even on the free plan. The actions log time, expenses and projects back in.
Verified Trustpilot reviews · AI, automation & growth agency
What the Noko Zapier integration does for you
Noko is a time tracker for teams that bill their hours: it shows who worked on what, how long, and whether that time is billable. Connected to Zapier, it talks to the rest of your tools in both directions. Noko events start automations elsewhere, and other apps can create entries, expenses and projects inside Noko.
Three results worth building. Billing that does not wait: New Invoice and Invoice Unpaid push invoice news to your accounting team the moment it happens. Time that logs itself: Create Entry turns a finished meeting or a closed ticket into a Noko entry, so nobody rebuilds the week from memory. Projects that open in one place: New Project mirrors a fresh Noko project into your task board, or Create Project does it the other way round when a deal is signed in your CRM.
The gaps are real too. The actions only create: Zapier cannot edit or delete an entry, an expense or a project in Noko, and it cannot create an invoice. Deletions and changes exist only as triggers, so you can react to them, not cause them. And a Zap never goes back in time: the hours you logged last month stay where they are.
To see how Zapier stacks up for this kind of work, read our Zapier review, or compare the billing models in n8n vs Zapier.
Zapier vocabulary in one minute
Eight terms you will see in the editor. Each is explained here once, then used as is.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap, like a new time entry in Noko. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, like Create Entry.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is counted in tasks.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is pushed by the app itself. All 14 Noko triggers are instant.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
- Search step
- A step that looks up something that already exists, like a Noko project, so later steps can use what it found.
- Connection
- Your Noko account linked to Zapier once, then reused by every step that reads from or writes to Noko.
What Noko costs you in Zapier tasks
Noko is not a premium app, so it works on the free plan, and its instant triggers skip the interval grid entirely.
- Free plan100 tasks per month, unlimited Zaps, two steps max
- Noko triggers14, all instant, no interval
- BilledEach successful action, never the trigger
- Premium appNo
The trigger never costs a task. You pay one task for each action that succeeds, such as Create Entry or a Slack message; a failed action costs nothing. The free plan builds two-step Zaps only: one trigger, one action. Add a filter, a search like Find Project or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid below only matters for the other app in your Zap if its trigger is a polling one; Noko's own triggers fire straight away on every plan.
Connect your Noko account in three steps
- 01
Open the connection dialog
Go to the Apps page of your Zapier account and click + Add connection. Have a Noko account ready, with access to the projects and invoices your Zaps will read or write.
- 02
Pick Noko
Type Noko in the search box of the dialog, select it from the results, then click Add connection. A new tab opens on the Noko side so you can sign in.
- 03
Sign in and grant access
Log in to Noko in that tab and allow Zapier to use the account. The connection then appears on the Apps page, and every Zap that touches Noko reuses it.
Your first Zap: flag big expenses the moment they land
GoalEvery Noko expense above your approval threshold is posted to the finance channel straight away.
- 01
Pick the Noko trigger
Build: create a Zap, choose Noko and the New Expense trigger, then select your Noko connection. It is instant, so there is no interval to set.
- 02
Test with a real expense
Test: Zapier brings back the three most recent expenses of your account. Pick a real one so the next steps are mapped on actual data.
- 03
Keep only the big ones
Add a Filter step: field = the expense price, a number rule, value = your threshold. A text rule here would never pass. The filter makes this a multi-step Zap, so it needs a paid plan.
- 04
Post to the finance channel
Add Slack and Send Channel Message. Map the project, the date and the price into the text so the approver sees everything without opening Noko.
- 05
Test and publish
Run each step once and check the message. When it reads well, click Publish. Expenses logged before that moment are not posted.
Noko triggers in Zapier
14 events start a Zap when something happens in Noko, and 14 of them are instant: the app calls Zapier straight away, whatever your plan.
Project Archived
Instant triggerIn Zapier“Triggers when a project is archived.”
Starts a Zap when someone archives a project in Noko, which usually means the work is over and the budget is closed. It is a clean signal for tidying up everything that lives around the project.
Deleted Entry
Instant triggerIn Zapier“Triggers when a time entry is deleted.”
Fires when a time entry disappears from Noko. Hours that vanish after a timesheet has been sent are exactly what a project lead wants to hear about before the client does.
Deleted Expense
Instant triggerIn Zapier“Triggers when an expense is deleted.”
Runs when an expense is removed from Noko. If your expenses also live in a bookkeeping sheet, this is the event that keeps both sides from drifting apart.
Deleted Invoice
Instant triggerIn Zapier“Triggers when an invoice is deleted.”
Picks up the deletion of an invoice in Noko. An invoice that disappears is rare and usually deliberate, which makes it worth a human glance every single time.
New Entry
Instant triggerIn Zapier“Triggers when a new time entry is logged.”
Each time someone logs time in Noko, this trigger starts a Zap. It is one of the triggers Zapier highlights for this app, and the one most teams start with, since entries are the raw material of every report.
New Expense
Instant triggerIn Zapier“Triggers when a new expense is logged.”
A new expense logged in Noko sets this one off, whether it is a train ticket or a software licence billed to a client. Zapier lists it among the highlighted triggers of the app.
New Invoice
Instant triggerIn Zapier“Triggers when a new invoice is logged.”
Runs as soon as an invoice is created in Noko. For a small agency, this is the bridge between tracked hours and the money that pays for them.
New Project
Instant triggerIn Zapier“Triggers when a new project is logged.”
Creating a project in Noko sets off this trigger. Zapier highlights it for this app, and it saves the classic double entry of setting the same project up in three tools.
Project Unarchived
Instant triggerIn Zapier“Triggers when a project is unarchived.”
Fires when an archived project comes back to life in Noko. A client returning for a second phase is the typical story, and it deserves the same setup as a new project.
Invoice Unpaid
Instant triggerIn Zapier“Triggers when an invoice is marked as unpaid.”
Catches the moment an invoice is marked as unpaid in Noko. That status change is the start of every follow-up, and the sooner someone knows, the sooner the reminder goes out.
Entry Changed
Instant triggerIn Zapier“Triggers when a time entry is changed.”
Any edit to an existing time entry in Noko sets it off: new minutes, a different project, a corrected description. It keeps any copy of your timesheets honest after the fact.
Expense Changed
Instant triggerIn Zapier“Triggers when an expense is changed.”
Reacts when an expense already in Noko is modified. A corrected amount or a project reassignment changes what gets billed, so your books need to follow.
Invoice Changed
Instant triggerIn Zapier“Triggers when any part of an invoice is changed.”
Fires whenever any part of a Noko invoice changes, from a line item to its status. It is the broadest invoice trigger, which makes it useful and noisy at the same time.
Project Changed
Instant triggerIn Zapier“Triggers when a time project is changed.”
Runs when a Noko project is edited, for instance a new name or a switch between billable and non-billable. Downstream tools that copied the old version need to hear about it.
Noko actions in Zapier
Noko gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Entry
ActionIn Zapier“Creates a new entry.”
Logs a new block of time in Noko from whatever another app knows: a meeting, a support ticket, a finished task.
Create Expense
ActionIn Zapier“Creates a new expense.”
Adds an expense to a Noko project. Costs then sit right next to the hours they belong to, which makes rebilling a client much simpler.
Create Project
ActionIn Zapier“Creates a new project.”
Opens a new project in Noko from a signed deal, a new client folder or a form.
Noko searches: find invoices, projects and users
3 search steps look for data that already exists in Noko, so a later step can use it.
Noko's three searches sit at the bottom of the Action event list, under the SEARCH heading. Use them when a later step needs a Noko record that no earlier step carried. Three settings decide what happens when a search does not find exactly one match.
Find Invoice
SearchIn Zapier“Finds an existing invoice.”
Looks up an invoice that already exists in Noko, so the next steps can read its details.
Find Project
SearchFind or createIn Zapier“Finds an existing project.”
Finds an existing Noko project, optionally narrowed by its billable or enabled status.
Find User
SearchIn Zapier“Finds an existing user.”
Retrieves a person from your Noko account, so a Zap can work with a specific teammate.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking it turns the search into a find-or-create. In Noko only Find Project offers it, shown in the editor as Find or Create Project.
- If multiple search results are found?Three ways out: keep the first match, which is the default, stop the Zap, or pass every match on at once.
When a Noko Zap breaks
Zapier links no help article to Noko, so the known failure points are Zapier's general rules, sharpened by how Noko works.
Four cases to check first, all tied to how Zapier itself works. For anything else, the Zapier troubleshooting page lists the usual suspects.
Last month's hours stay put
A Zap only reacts to what happens after you publish it. Entries, expenses and invoices that already exist in Noko are never picked up; moving them is a separate job.A Zap that feeds itself
A Zap on New Entry that also runs Create Entry starts itself again with every entry it writes, and burns through your tasks fast.Bulk changes held back
Editing a large batch of entries or invoices at once can send a flood of events. Zapier's flood protection may hold them back instead of running them all.Edits retrigger everything
Entry Changed, Expense Changed and Invoice Changed fire on every edit. A filter keeps the Zap from rerunning its actions on trivial fixes.
Need help automating Noko with Zapier?
A person reads every message.



