- Home
- Resources
- Integrations
- Nomisma
Nomisma Zapier integrationAutomate Nomisma with Zapier.
The Nomisma Zapier integration gives you 0 triggers, 2 actions and 0 searches. Zapier can file a supplier bill or drop a receipt into Nomisma for you, but the Zap always has to start in another app, and the free plan is enough to try it.
Verified Trustpilot reviews · AI, automation & growth agency
What the Nomisma Zapier integration actually does
Nomisma is accounting software that covers the whole ledger of a company. Its Zapier integration works in one direction only: something happens in another tool, and Zapier writes the result into Nomisma as a supplier bill or as a receipt waiting to be processed.
Two actions, both built to cut retyping. Three outcomes you can actually get:
Supplier bills that enter themselves. When a bill arrives somewhere else, in a form or a spreadsheet for example, Create Bill records it in Nomisma with supplier, date, amounts and tax.
Receipts that stop living in inboxes. A receipt file saved or received in another app goes straight into Nomisma's pending receipts through Upload Receipt.
One entry point for several companies. Both actions ask which company they write to, so one Zap per company keeps the books apart.
Now what Zapier does not do here. Nomisma has no trigger, so nothing that happens inside Nomisma can start a Zap: a paid bill or a new entry stays invisible to Zapier. There is no search either, so a Zap cannot look up a supplier or a bill already in the books. And the two actions only create; nothing edits or deletes. If you need the other direction, the Zapier alternatives page helps check whether another tool reaches further. For a wider view of the platform, see the Zapier review.
Zapier vocabulary in one minute
Seven words come back on every Zapier page. Here they are in plain English, once, so the rest reads easily.
- Zap
- The automation you build on Zapier: a trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. With Nomisma, it always comes from another app, since Nomisma has none.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you, here a bill or a receipt.
- Task
- What Zapier bills: one action your Zap completes successfully. The number on your plan counts exactly those.
- Polling vs instant trigger
- A polling trigger is checked on a timer. An instant trigger is reported by the app itself, the moment the event happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it quietly otherwise.
- Search step
- A step that looks up something already stored in an app, so the steps after it can reuse what it found.
What a Nomisma Zap really costs
Every bill or receipt Zapier writes into Nomisma costs one task, and only if it works.
- Trigger (other app)Free, never counted
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, works on the free plan
The trigger in the other app never costs anything, however often it checks. Each Nomisma action that goes through counts as one task; one that fails is not billed. A Zap that creates a bill and uploads its receipt uses two tasks per run. The free plan gives 100 tasks a month and unlimited Zaps, and Nomisma is not a premium app, so it is allowed there. The limit is the shape: on the free plan a Zap stays at two steps, one trigger and one action. Both Nomisma actions in one Zap, or a filter in front, make it a multi-step Zap, which needs a paid plan.
Connect Nomisma to Zapier in 3 steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Nomisma account linked once, then reused by every step that needs it.
- 02
Pick Nomisma
Type Nomisma in the search box of the dialog, select it, then click Add connection. A new tab opens on the Nomisma side. You need an existing Nomisma account at this point.
- 03
Sign in and allow access
Log in to Nomisma in that tab and grant Zapier access. If you keep the books of a company you do not own, make sure your account has write rights on it, or the actions will have nowhere to write.
Your first Zap with Nomisma
GoalSend every receipt that lands in your mailbox to Nomisma's pending receipts.
- 01
Build: pick the starting app
Create a Zap and choose the app where receipts show up, then the event that starts the Zap there. Nomisma cannot fill this slot, it has no trigger.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of that account, so you can pick a real receipt to map from in the next step.
- 03
Build: add Nomisma
Add Nomisma as the action app and pick Upload Receipt. Choose the company, then map the file name, extension and path from the item the trigger found.
- 04
Test the action
Run the action once and open Nomisma: the receipt should sit in the pending receipts of the right company. If it does not, fix the mapping now.
- 05
Publish
Click Publish to switch the Zap on. From then on, each new receipt in the starting app is sent to Nomisma, at the pace of that app's trigger.
The Nomisma actions
Nomisma gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Bill
ActionIn Zapier“Create supplier bill”
Records a supplier bill in Nomisma for the company you choose, with its supplier, currency, date, expense type, description, gross total and tax amount.
Upload Receipt
ActionIn Zapier“Upload Receipt in Pending Receipt.”
Drops a receipt file into Nomisma's pending receipts for a given company, ready for someone to process later in the app.
When a Nomisma Zap breaks
Zapier lists no help article and no app-specific limit for Nomisma. The cases below come from how Zapier works in general, plus the required fields of the two actions.
Four situations explain most of the surprises. None of them shows up as an obvious error on day one. If one of them bites anyway, the Zapier troubleshooting guide walks through the fixes.
Old bills and receipts never come through
A Zap only reacts to what happens after it is switched on. Documents that existed before you published stay where they were, and moving them is a separate job.An empty field stops the action
Every field of both actions is mandatory. When the starting app leaves one empty, the action fails for that run, and a failed action is not billed.The Zap keeps restarting itself
If the Zap writes back into the place its own trigger watches, it sets itself off again and again and burns through your task count quickly.A big batch gets held back
When the starting app suddenly sends a huge batch, after an import or a migration for example, Zapier's flood protection can hold it back.
Need help automating Nomisma with Zapier?
A person reads every message.



