Resources · Zapier integration

Nagaris Zapier integrationAutomate Nagaris with Zapier.

The Nagaris Zapier integration gives you 42 triggers and 123 actions, and no search step. Every trigger is checked on a timer, so this page tells you what each one does, what it costs and where it trips up before you build anything.

See the 165 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Nagaris Zapier integration actually does

Nagaris is a client database built for accounting firms in Australia, sold on keeping client records clean across every tool a firm runs. Zapier links it to your other apps: something changes in Nagaris and Zapier passes it on, or something happens elsewhere and Zapier writes it into Nagaris. All of it runs through Zaps you build once.

Three examples show the range. First, a client file that opens itself: a form signed in another tool can create the group in Nagaris with Create Client Group, flagged as a prospect or not, so nobody retypes the name. Second, a handover nobody forgets: New Handovers Created can push each handover into the place your team already reads. Third, structures kept in step: a new trust, SMSF or partnership in Nagaris can be copied into a register you keep elsewhere, using the matching New ... Created trigger.

Now what Zapier does not do for Nagaris. None of the 42 triggers is instant: Zapier checks on a timer, and that timer depends on your plan. There is no search step either, so a Zap cannot look up an existing client by name before it writes; the Get and List actions read by ID or pull everything, and they count as actions. And the integration never reaches back into history: a Zap only sees what changes after you switch it on.

If you are still weighing tools, see our n8n vs Zapier comparison or our Zapier review before you commit a client database to one of them.

Vocabulary

Zapier words you will meet on this page

Eight terms. Learn them once, they come back in every block below.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and nothing else.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling trigger
A trigger Zapier checks on a timer, keeping only items it has not seen yet. Every Nagaris trigger works this way.
Filter
A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Connection
Your Nagaris account linked to Zapier once, then reused by every step of every Zap that touches Nagaris.
Cost

What a Nagaris Zap really costs

Zapier bills tasks, not checks. The trigger never costs anything, however often Zapier looks into Nagaris.

  • Tasks on the free plan100 per month
  • Zaps on the free planUnlimited, two steps each
  • Cost of a trigger check0 tasks
  • Premium appNo, free plan works

Each action that goes through counts as one task, and a three-action Zap eats three times what a one-action Zap does. An action that fails is not counted. Nagaris is not a premium app, so it runs on the free plan, but that plan builds two-step Zaps only: one trigger, one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The interval below is how often Zapier checks a polling trigger, and all 42 Nagaris triggers are polling.

Connect

Connect Nagaris to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. You need an account on Nagaris, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Pick Nagaris

    Type Nagaris in the search box of the dialog, select it in the results, then click Add connection. A new browser tab opens so you can sign in to Nagaris itself.

  3. 03

    Sign in and grant access

    Sign in to Nagaris in that tab and grant Zapier access to the account. The connection is then saved once and offered to every Zap step that uses Nagaris.

First Zap

Your first Nagaris Zap: log every new client group in a spreadsheet

GoalEach new client group in Nagaris becomes a row in your tracking spreadsheet, and your team chat hears about it.

  1. 01

    Create the Zap

    Start a new Zap and pick Nagaris as the app that starts it. Choose New Client Group Created as the event, then select your Nagaris connection.

  2. 02

    Set the trigger

    Fill in the Organization ID the trigger asks for. Testing brings back the three most recent client groups of the account, so you map the next steps on a real one.

  3. 03

    Add the spreadsheet row

    Add your spreadsheet as the action and pick the columns to fill. Check at test which details of the group the trigger actually carries before you map them.

  4. 04

    Tell the team

    Add your chat app as a third step. Three steps make this a multi-step Zap, so it needs a paid plan; on the free plan, stop after the spreadsheet row.

  5. 05

    Test, then publish

    Run each step once and read what came back. When the row shows up in your spreadsheet, click Publish to switch the Zap on.

Triggers

Nagaris triggers on Zapier

42 events start a Zap when something happens in Nagaris. Zapier checks for them at the interval your plan allows.

1

New Address Created

Polling trigger

In Zapier“Triggers when a new address is created.”

Any address added to Nagaris starts the Zap, so your other tools hear about it without anyone retyping it; the test shows which details it carries.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a mailing tool or a register kept outside Nagaris needs every new address that Zapier picks up.
Watch out
the Organization ID is required, so pick the organisation before you run the first test.
2

Address Updated

Polling trigger

In Zapier“Triggers when an address is updated.”

Edits matter as much as new entries: this one wakes up when an existing address record changes in Nagaris, whoever made the change.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a corrected postcode or street name has to follow into the copy of that address you keep in another app.
Watch out
an update Zap only sees changes made after it is published, never the edits that came before.
3

New Client Contact Created

Polling trigger

In Zapier“Triggers when a new client contact is created.”

Linking a contact to a client in Nagaris creates a client contact record, and that new link is what starts this Zap.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when your newsletter or calling list should gain each person newly tied to a client, without a weekly export.
Watch out
without the Organization ID filled in, the trigger cannot be tested or switched on.
4

Client Contact Updated

Polling trigger

In Zapier“Triggers when a client contact is updated.”

Changes to the link between a contact and a client, such as who is marked as the primary contact, set this trigger off.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a sheet of primary contacts per client has to stay right after someone reshuffles them in Nagaris.
Watch out
the test brings back recent items of the account, so check which one you map on.
5

New Client Document Created

Polling trigger

In Zapier“Triggers when a new client document is created.”

Each document record that appears on a client in Nagaris launches the Zap; run the test to see which details come with it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when you want a message every time a client document lands, instead of opening the record to check.
Watch out
the Organization ID is mandatory here, as on almost every Nagaris trigger.
6

Client Document Updated

Polling trigger

In Zapier“Triggers when a client document is updated.”

Renaming a client document or changing whether it is still requested counts as an update in Nagaris, and fires this trigger.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a checklist kept outside Nagaris should mirror the current state of each client document.
Watch out
a Zap that writes back into client documents can set this trigger off again, so keep the action on another record.
7

New Client Email Created

Polling trigger

In Zapier“Triggers when a new client email is created.”

Adding an email address to a client record in Nagaris is the event this Zap listens for, one run per address.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when your email tool should receive each new client address without someone exporting a list from Nagaris.
Watch out
addresses that existed before the Zap was published are never picked up.
8

Client Email Updated

Polling trigger

In Zapier“Triggers when a new client email is updated.”

Fix a typo in a client email, or switch which address is the primary one, and this trigger notices the change on its next check.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a mailing list must stop sending to an address the firm has since corrected.
Watch out
fill in the Organization ID first, or there is nothing to test.
9

New Client Group Contact Created

Polling trigger

In Zapier“Triggers when a new client group contact is created.”

Groups have contacts of their own in Nagaris, and attaching a person to a client group starts this Zap.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when the people attached to a whole client group, not to a single client, need adding to a list your team shares.
Watch out
the Organization ID is required before the first test can bring anything back.
10

Client Group Contact Updated

Polling trigger

In Zapier“Triggers when a client group contact is updated.”

Here the Zap reacts when a contact already tied to a client group is changed, for example made visible or editable for the client.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when every change of access granted to a client should be logged somewhere your team reviews.
Watch out
the Organization ID is required before the test can bring anything back.
11

New Client Group Created

Polling trigger

In Zapier“Triggers when a new client group is created.”

A fresh client group in Nagaris starts this Zap, one run per group, prospect or not.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when onboarding steps, such as a first document request or a welcome message, should start from the group itself.
Watch out
groups created before the Zap went live never start it, so plan a separate job for them.
12

New Client Group Document Created

Polling trigger

In Zapier“Triggers when a new client group document is created.”

Documents can sit on a client group rather than on one client, and every new one of those starts this Zap.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a paper requested at group level should appear on a shared tracker.
Watch out
the Organization ID is required on this trigger, as on its neighbours.
13

New Client Group Document Updated

Polling trigger

In Zapier“Triggers when a client group document is updated.”

Despite the word New in its name, this trigger is about changes: it fires when a client group document is updated.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a group document flagged as requested is renamed or switched, and your tracker should follow it.
Watch out
pick it from the list by its full label, because the name is easy to confuse with the creation trigger.
14

Client Group Updated

Polling trigger

In Zapier“Triggers when a client group is updated.”

Whenever a client group is renamed in Nagaris, or switched between prospect and finalised, this trigger sets the Zap going.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a sales pipeline kept outside Nagaris should move a card once a prospect group is converted.
Watch out
a Zap that also updates client groups can retrigger itself, so think twice before writing back.
15

New Client Notes Created

Polling trigger

In Zapier“Triggers when a new client notes is created.”

A note written on a client in Nagaris becomes the starting point of a Zap; the test shows what it carries.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when every new client note should be copied into a shared log or a chat channel the team reads.
Watch out
enter the Organization ID before the test, it is mandatory.
16

Client Notes Updated

Polling trigger

In Zapier“Triggers when a client notes is updated.”

When a note already written on a client is edited in Nagaris, this trigger picks the new version up on its next check.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when the copy of a note kept outside Nagaris should never drift away from the original wording.
Watch out
only edits made after publishing reach the Zap; older rewrites stay where they are.
17

New Client Phone Created

Polling trigger

In Zapier“Triggers when a new client phone is created.”

Whenever someone adds a phone number to a client record, the Zap starts; check at test which details come through.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a calling or texting tool needs the number of each client once it is on file in Nagaris.
Watch out
the Organization ID field must be filled in before anything can be tested.
18

Client Phone Updated

Polling trigger

In Zapier“Triggers when a client phone is updated.”

Corrected or swapped phone numbers on a client fire this trigger, one run per changed number.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a phone directory shared with the team should always keep the latest number for each client.
Watch out
older changes are not replayed once the Zap is switched on.
19

Company Updated

Polling trigger

In Zapier“Triggers when a new company is updated.”

Company clients carry several registration flags in Nagaris, and any change to a company record starts this Zap.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a switch on a company, such as its GST registration, should be logged in the tool where you track company registrations.
Watch out
the trigger needs the Organization ID before it can test or run.
20

Contact Updated

Polling trigger

In Zapier“Triggers when a contact is updated.”

This one watches contacts themselves, not their link to a client: edit a contact in Nagaris and the Zap runs.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a CRM kept outside Nagaris should receive the corrected details of a person.
Watch out
the Organization ID is required, as on almost every Nagaris trigger.
21

New Client Address Created

Polling trigger

In Zapier“Triggers when a new client address is created.”

Different from the plain address trigger, this one fires when an address is attached to a client record.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when you only care about addresses that belong to a client, and not loose address records.
Watch out
fill in the Organization ID, it is required to set the trigger up.
22

Client Address Updated

Polling trigger

In Zapier“Triggers when an client address is updated.”

Changes to an address already linked to a client are what this trigger reports to Zapier.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a client moves and the postal tool that sends their letters must follow the new address.
Watch out
addresses edited before the Zap was live are skipped, whatever their date.
23

Individual Updated

Polling trigger

In Zapier“Triggers when an individual is updated.”

Edits to an individual client in Nagaris, whatever the field, start this Zap, one run per edited person.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a change to a person, such as their resident status for tax, should be flagged in the tool where you follow that client.
Watch out
the Organization ID must be set before the test.
24

New Company Created

Polling trigger

In Zapier“Triggers when a new company is created.”

A company added as a client in Nagaris becomes a new run of the Zap, one per company.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when each new company client should open a folder or a card in your project tool.
Watch out
companies already in Nagaris before publishing are not sent, only those created afterwards.
25

New Contact Created

Polling trigger

In Zapier“Triggers when a new contact is created.”

Whoever types a new person into the Nagaris contact list sets this one off, before that person is linked to any client.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when your email marketing tool should gain each contact the firm records.
Watch out
the Organization ID is required to set it up and test it.
26

New Handovers Created

Polling trigger

In Zapier“Triggers when a new handovers is created.”

Each new handover written in Nagaris starts this Zap, one run per handover.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when every new handover should also land in a team inbox or chat, so nobody has to open Nagaris to see it.
Watch out
handovers created before the Zap went live are never sent.
27

New Individual Created

Polling trigger

In Zapier“Triggers when a new individual is created.”

Adding a person as a client in Nagaris is the cue for this Zap, one run per new individual.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when every new individual client should become a row in a shared spreadsheet.
Watch out
the Organization ID must be filled in before testing, or the trigger stays empty.
28

Organisation Updated

Polling trigger

In Zapier“Triggers when an organisation is updated.”

Changes made to an organisation in Nagaris, such as a new name, fire this trigger, one run per changed organisation.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when you want a record of every change made at organisation level.
Watch out
changes made before the Zap is published are never replayed.
29

New Other Entities Created

Polling trigger

In Zapier“Triggers when an other entity is created.”

Each new client filed under the other entity type in Nagaris starts the Zap, one run per record.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when each new other entity should be flagged in a list you review by hand.
Watch out
the Organization ID is required here too.
30

Other Entities Record Updated

Polling trigger

In Zapier“Triggers when an other entity record is updated.”

An edit to an other entity record in Nagaris shows up here as a new run of the Zap.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a register of these entities kept outside Nagaris has to stay in line with the source.
Watch out
edits made before the Zap was published never come through.
31

New Package Created

Polling trigger

In Zapier“Triggers when a new package is created.”

Packages tie an amount to a client group in Nagaris, and creating one starts this Zap, one run per package.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when your invoicing tool should hear about each new package created for a client group.
Watch out
set the Organization ID first, the trigger requires it.
32

Package Updated

Polling trigger

In Zapier“Triggers when a package is updated.”

Changing the amount, the name or the active state of a package sends that package through this trigger.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a revised package amount should reach the tool where you invoice it.
Watch out
a Zap that writes into the place its own trigger watches can set itself off again, so send the change elsewhere.
33

New Partnership Created

Polling trigger

In Zapier“Triggers when a new partnership is created.”

A partnership set up as a client in Nagaris kicks off this Zap, one run per partnership.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when each new partnership should open a checklist in another tool, so the steps that follow its creation are not forgotten.
Watch out
fill in the Organization ID or the test stays empty.
34

Partnership Updated

Polling trigger

In Zapier“Triggers when a partnership is updated.”

Edit a partnership client in Nagaris and Zapier picks the change up on its next check.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a change of name or registration on a partnership must reach your practice register.
Watch out
older edits are not replayed once the Zap is on.
35

New Service Created

Polling trigger

In Zapier“Triggers when a new service is created.”

Every service added in Nagaris starts this Zap, one run per service.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when your billing or quoting tool should list each service the team defines in Nagaris, without a second entry by hand.
Watch out
the Organization ID is required before the trigger can be tested.
36

Service Updated

Polling trigger

In Zapier“Triggers when a service is updated.”

Turning a service off, renaming it or switching it to billable fires this trigger once per changed service.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a price list kept elsewhere should drop the services marked inactive in Nagaris.
Watch out
the Organization ID is required, as on the creation trigger.
37

New SMSF Created

Polling trigger

In Zapier“Triggers when a new SMSF is created.”

SMSFs have their own client type in Nagaris, and each new one starts the Zap.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when each new SMSF should be announced in your team chat or added to a list kept elsewhere.
Watch out
the Organization ID has to be filled in first.
38

SMSF Updated

Polling trigger

In Zapier“Triggers when a SMSF is updated.”

Any change on an SMSF client record reaches the Zap through this trigger, one run per edited record.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when an SMSF list kept outside Nagaris must reflect each edit made in Nagaris.
Watch out
only edits made after the Zap is published come through.
39

New Sole Trader Created

Polling trigger

In Zapier“Triggers when a new sole trader is created.”

Sole traders are their own client type in Nagaris, and adding one sets this trigger off, one run each.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when each new sole trader should get a welcome email from your mailing tool, without anyone sending it by hand.
Watch out
the Organization ID is mandatory on this trigger.
40

Sole Trader Updated

Polling trigger

In Zapier“Triggers when a sole trader is updated.”

Edits to a sole trader record are passed to the Zap by this one.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a change of GST registration on a sole trader should be noted in the tool where you follow that client.
Watch out
nothing edited before the Zap was published will come through.
41

New Trust Created

Polling trigger

In Zapier“Triggers when a new trust is created.”

Trusts added as clients in Nagaris start this Zap, one run per trust; the test shows what each run carries.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when each new trust should open a task in your project tool, so nobody has to watch the client list by hand.
Watch out
enter the Organization ID before testing.
42

Trust Updated

Polling trigger

In Zapier“Triggers when a trust is updated.”

Last in the list, this trigger runs when a trust client is edited in Nagaris.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when a trust register kept by the team has to follow each change.
Watch out
the Organization ID must be filled in before the first test, or there is nothing to map.
Actions

Nagaris actions on Zapier

Nagaris gives you 123 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Delete Trust

Action

In Zapier“Deletes a trust by id.”

Deletes a trust client from Nagaris, picked out by its Trust UUID.

When to use it
when a trust should leave the client list for good.
Watch out
the Trust UUID is required, so the Zap must know exactly which trust goes.
2

Create Client Email

Action

In Zapier“Creates new client email.”

Adds an email address to a client, and can mark it as the primary address for that client.

When to use it
when a client gives a new address through a form and it should be stored on the right record.
Watch out
Client UUID and Email Address are required.
3

Create a Trust

Action

In Zapier“Creates a new trust.”

Records a new trust as a client inside a client group, with the usual flags for prospects and clean-up.

When to use it
when the trust details arrive through another app and the trust should exist in Nagaris before the trustees are added.
Watch out
the Client Group UUID is required on top of the Organisation ID.
4

Create an Address

Action

In Zapier“Creates a new address.”

Creates a standalone address record in Nagaris, not yet tied to any client.

When to use it
when an address collected in another tool should exist in Nagaris as a record of its own.
Watch out
only the Organisation ID is marked as required, so check at test what the new address keeps.
5

Create a Service Tag

Action

In Zapier“Creates a service tag.”

Creates a service tag in Nagaris, with a name and a switch for whether it is active.

When to use it
when your tagging scheme lives elsewhere and new tags should appear in Nagaris too.
Watch out
only Name and the Organisation ID are required.
6

Create Client Address

Action

In Zapier“Creates a client address.”

Links an address record of Nagaris to a client, so it shows on that client's file.

When to use it
when an address created earlier should now belong to a specific client record.
Watch out
it needs both an Address UUID and a Client UUID.
7

Create a Client Contact

Action

In Zapier“Creates a new client contact.”

Links a contact to a client, optionally as the primary one or with verification required.

When to use it
when a contact already on file should be attached to the right client from another tool.
Watch out
both the Contact UUID and the Client UUID are required, together with the Organisation ID.
8

Create Client Group

Action

In Zapier“Creates a new client group in the system.”

Opens a new client group in Nagaris; the other client types ask for a Client Group UUID when they are created.

When to use it
when a form signed in another tool should create the group in Nagaris, flagged as prospect or not.
Watch out
Organisation ID and Name are both required fields.
9

Create Client Group Contact

Action

In Zapier“Creates a new client group contact.”

Attaches a contact to a whole client group, with options for client visibility and editing.

When to use it
when one person should be attached to a whole client group rather than to a single client.
Watch out
needs a Contact ID and a Client Group UUID, both taken from earlier steps or typed in.
10

Create Client Group Document

Action

In Zapier“Creates a client group document.”

Adds a document entry to a client group, optionally marked as requested from the client.

When to use it
when every new group should start with the list of papers the firm will ask for.
Watch out
Client Group UUID and Name are required.
11

Create Client Note

Action

In Zapier“Creates a client note.”

Writes a note on a client, filled with whatever content you map into it from earlier steps.

When to use it
when a call summary or an email from another app should be kept on the client file.
Watch out
Content and Client UUID are required.
12

Create Client Phone

Action

In Zapier“Creates new client phone.”

Stores a phone number on a client record, with an option to make it the primary number.

When to use it
when your call or booking tool captures a number that belongs in Nagaris.
Watch out
the Client UUID has to come from an earlier step, because typed IDs are easy to get wrong.
13

Create Client Service

Action

In Zapier“Creates a client service.”

Assigns a service from the catalogue to a client, from a given start date onwards.

When to use it
when an accepted proposal should switch on the matching service for that client.
Watch out
Start Date is required, along with the Service UUID and the Client UUID.
14

Create Client Trustee

Action

In Zapier“Creates a new client trustee.”

Records a trustee for a client by linking a trustee record to the client record.

When to use it
when trustee details collected outside Nagaris should complete a trust record.
Watch out
it asks for a Client UUID and a Trustee UUID, plus the Organisation ID.
15

Create Client Website

Action

In Zapier“Creates new client website.”

Saves a website address against a client, primary or not, so the team finds it on the file.

When to use it
when a business client sends its site in an onboarding form.
Watch out
Website URL and Client UUID are both required fields.
16

Create a Company

Action

In Zapier“Creates a new company.”

Creates a company client, with room for its registrations such as GST, FBT or payroll tax.

When to use it
when an onboarding form for business clients should produce the company record directly.
Watch out
Client Group UUID and Client Name are required on top of the Organisation ID.
17

Create Contact

Action

In Zapier“Creates a new contact.”

Adds a person to the Nagaris contact list, ready to be linked to one or more clients later on.

When to use it
when a web form or a booking tool collects someone the firm should keep on file.
Watch out
only the Organisation ID is marked as required, so check at test what the record keeps.
18

Create a Handover

Action

In Zapier“Creates a new handover.”

Writes a handover on a client group, with a sender, a subject and a body.

When to use it
when an email or a form about a file should become a handover in Nagaris.
Watch out
Email From, Subject and Body are all required.
19

Create a Individual

Action

In Zapier“Creates a new individual.”

Turns a person into an individual client inside a client group. The odd grammar of the label is how Zapier shows it.

When to use it
when a new individual client should exist in Nagaris once an intake form is filled in.
Watch out
it needs a Client Group UUID and a Contact UUID, two identifiers to fill in before the test.
20

Create Organisation

Action

In Zapier“Creates an organisation.”

Sets up a new organisation in Nagaris from a single required field: its name.

When to use it
when a new organisation should be created from a form or a spreadsheet row.
Watch out
Name is the only required field, so check its spelling before the test step.
21

Create Other Entity

Action

In Zapier“Creates a new other entity.”

Creates a client of the other entity type inside a client group, with the same flags as the other client types.

When to use it
when a client of that type arrives through another app and should be on file in Nagaris.
Watch out
like the other client types, it needs a group and a name besides the Organisation ID.
22

Create a Package

Action

In Zapier“Creates a new package.”

Creates a package with a name and an amount, attached to a client group.

When to use it
when a fee agreed in your quoting tool should become a package in Nagaris.
Watch out
Amount is required, so make sure the mapped value is a number.
23

Create Partnership

Action

In Zapier“Creates a partnership.”

Adds a partnership as a client of the firm, placed under a client group of your choice.

When to use it
when partnerships come in through a separate intake form and should land in Nagaris with no copy and paste.
Watch out
a client name and a group are required, along with the Organisation ID.
24

Create a Service

Action

In Zapier“Creates a new service.”

Adds a service to the catalogue of the firm, billable or not, active or not.

When to use it
when the service list is maintained in a spreadsheet and Nagaris should follow it.
Watch out
Service Name is required besides the Organisation ID.
25

Create New SMSF

Action

In Zapier“Creates a new SMSF .”

Creates an SMSF as a client record, with the same flags as the other client types.

When to use it
when SMSF details collected in a sheet should be pushed into Nagaris, one record each.
Watch out
the SMSF must sit in a client group, so fill in a Client Group UUID.
26

Create Sole Trader

Action

In Zapier“Creates a sole trader.”

Registers a sole trader as a client, with the usual flags such as prospect or GST registered.

When to use it
when sole trader sign-ups from your website should become clients without retyping.
Watch out
Client Name and Client Group UUID are both required.
27

Delete a Client Address

Action

In Zapier“Deletes a client address by id.”

Breaks the link between an address and a client by deleting the client address record.

When to use it
when an old address should stop showing on a client.
Watch out
the Client Address UUID is required, not the Address ID.
28

Delete a Client Contact

Action

In Zapier“Deletes a client contact by id.”

Unlinks a contact from a client by removing the client contact record, not the contact itself.

When to use it
when a person leaves a client business and should no longer appear on that file.
Watch out
needs the Client Contact UUID, not the Contact ID.
29

Delete a Client Document

Action

In Zapier“Deletes a client document by id.”

Cancels a document record on a client by deleting it.

When to use it
when a request was made by mistake and should not reach the client.
Watch out
needs the Client Document UUID, not the Client UUID, to say which document goes.
30

Delete Client Email

Action

In Zapier“Deletes a client email by id.”

Strips an email record from a client, by its own ID.

When to use it
when an address bounces for good in your mailing tool and should go.
Watch out
needs the Client Email UUID, the ID of the email record itself, not of the client.
31

Delete Client Group

Action

In Zapier“Deletes a client group by id.”

Removes a client group by its ID.

When to use it
when a prospect group is dropped in your CRM and should not linger in Nagaris.
Watch out
the Client Group ID is required, so the Zap must know exactly which group to remove.
32

Delete Client Group Contact

Action

In Zapier“Deletes a client group contact.”

Detaches a contact from a client group, leaving the contact itself in place in Nagaris.

When to use it
when access granted to a group contact should end.
Watch out
the Client Group Contact UUID is required to say which link.
33

Delete a Client Group Document

Action

In Zapier“Deletes a client group document by id.”

Withdraws a document held at client group level by deleting its record.

When to use it
when a request made at group level is cancelled and the document should no longer show on the group.
Watch out
the Client Group Document UUID is required to say which document goes.
34

Delete Client Phone

Action

In Zapier“Deletes a client phone by id.”

Takes a phone number off a client by deleting its phone record.

When to use it
when a number is reported as no longer in use.
Watch out
the Client Phone UUID is required, not the client's own ID, so the Zap must know which number record to remove.
35

Delete a Client Service

Action

In Zapier“Deletes a client service by id.”

Stops a service assigned to a client by deleting the assignment.

When to use it
when an engagement ends and the service should no longer be billed to that client.
Watch out
the Client Service UUID is required, not the ID of the service itself.
36

Delete a Client Trustee

Action

In Zapier“Delete a client trustee by id.”

Ends a trustee link on a client by deleting the client trustee record.

When to use it
when a trustee steps down and the trust record should stop naming them.
Watch out
needs the Client Trustee UUID, not the Trustee UUID alone.
37

Delete a Client Website

Action

In Zapier“Deletes a client website by id.”

Removes a website record from a client, by its own ID, without touching the client.

When to use it
when a business client closes its site and the address should not stay on file.
Watch out
needs the Client Website UUID.
38

Delete a Company

Action

In Zapier“Deletes a company by id.”

Erases a company client from Nagaris, found by its Client UUID.

When to use it
when a duplicate company spotted during a review in another tool should be cleared.
Watch out
the Client UUID must come from a reliable earlier step, never a guess.
39

Delete Individual

Action

In Zapier“Delete an individual by id.”

Takes an individual client out of Nagaris by its ID.

When to use it
when a cleanup list kept in a spreadsheet flags a person entered twice.
Watch out
map the Client UUID from a reliable step, never a typed guess.
40

Delete Other Entity

Action

In Zapier“Deletes an other entity by id.”

Deletes a client filed as an other entity, by its ID.

When to use it
when such a structure is closed and its record should not linger.
Watch out
the Other Entity UUID is required, so the Zap must know exactly which record to remove.
41

Delete a Package

Action

In Zapier“Deletes a package by id.”

Deletes a package from Nagaris, one package per run. A package is created with a name, an amount and a Client Group UUID.

When to use it
when a package should no longer be on file.
Watch out
the required fields are the Organisation ID and a Contact ID.
42

Delete Partnership

Action

In Zapier“Deletes a partnership by id.”

Drops a partnership client from the database, found by its Partnership UUID.

When to use it
when a partnership is closed in your practice register and should go from Nagaris too.
Watch out
the Partnership UUID is required, so the Zap must know which partnership to remove.
43

Delete a Service

Action

In Zapier“Deletes a service by id.”

Retires a service from the catalogue of the firm by deleting it.

When to use it
when the firm stops offering it and the price list kept elsewhere already shows that.
Watch out
needs the Service ID, mapped rather than typed.
44

Delete Service Tag

Action

In Zapier“Deletes a service tag by id.”

Gets rid of a service tag that no longer sorts anything.

When to use it
when a tag falls out of your sorting scheme.
Watch out
the Service UUID is required, so check at test that the right tag is removed.
45

Delete SMSF

Action

In Zapier“Deletes a SMSF by id.”

Wipes an SMSF client from Nagaris by its ID.

When to use it
when a fund marked as closed in your SMSF tracker should go from Nagaris too.
Watch out
the SMSF UUID is required to say which fund goes.
46

Delete Sole Trader

Action

In Zapier“Deletes a sole trader by id.”

Clears a sole trader client away from the database.

When to use it
when a duplicate trader record found during a review should be cleared.
Watch out
needs the Sole Trader UUID to say which record goes, so check the value before you publish.
47

Get an Address

Action

In Zapier“Get an address by id.”

Fetches one address record by its ID and passes what Nagaris returns to the next steps.

When to use it
when you hold an address ID and a later step needs the address itself.
Watch out
the Address ID is required, so check at test that the right address comes back.
48

List Addresses

Action

In Zapier“List all addresses.”

Brings every address record of the organisation into the Zap, linked to a client or not.

When to use it
when a mailing tool needs the full address book in one go.
Watch out
the Organization ID is required to run it.
49

List Clients

Action

In Zapier“List all clients .”

Brings back the clients of an organisation in one step, so a single action reads the whole client list.

When to use it
when an export of the client base should feed a spreadsheet.
Watch out
the Organization ID is required, and the step counts as a task each time it succeeds.
50

List Client Group Contacts

Action

In Zapier“List all client groups contacts.”

Rounds up all the contacts attached to client groups in the organisation.

When to use it
when a mailing to client group contacts needs every one of them.
Watch out
the Organization ID is required, and the run counts as a task.
51

List Companies

Action

In Zapier“List all companies.”

Gathers every company client of the organisation into one result.

When to use it
when a review of company registrations starts from a full extract placed in a spreadsheet.
Watch out
the Organization ID is required, and a second action after this one makes the Zap multi-step.
52

List Contacts

Action

In Zapier“List all contacts.”

Collects all contacts held in an organisation, linked to a client or not.

When to use it
when a mailing tool needs a pull of every contact the firm keeps in Nagaris.
Watch out
a Zap only runs on its trigger, so plan which event starts this pull and how often it happens.
53

List Handovers

Action

In Zapier“List all handovers.”

Gathers all the handovers of the organisation into one result.

When to use it
when you want the handover history in one sheet for a review.
Watch out
each successful run counts as one task, and the Organization ID is required.
54

List Individual

Action

In Zapier“List all individuals.”

Returns the individual clients of an organisation in one result.

When to use it
when a list of individual clients should be rebuilt in a sheet.
Watch out
the label is singular in the editor, so search for List Individual when you add the step.
55

List Other Entities

Action

In Zapier“List all other entities.”

Enumerates the clients filed under the other entity type in the organisation.

When to use it
when you audit those clients and want them in one place.
Watch out
the Organization ID is required; check at test what the list carries.
56

List Packages

Action

In Zapier“List all packages.”

The packages of the organisation come back from this single step.

When to use it
when a fee review should start from every package on file, laid out in one sheet.
Watch out
the Organization ID is required, and the run costs a task.
57

List Partnerships

Action

In Zapier“List all partnerships.”

Returns all partnership clients of the organisation in a single step.

When to use it
when you want the partnerships laid out in a sheet.
Watch out
the Organization ID is required; check at test how the list comes back before mapping it.
58

List Services

Action

In Zapier“List all services.”

Lays out every service of the catalogue in one result.

When to use it
when your price list should be compared with the services defined in Nagaris.
Watch out
the Organization ID is required, and the run counts as a task.
59

List Service Tags

Action

In Zapier“List all service tags.”

Returns the service tags defined in the organisation in one step.

When to use it
when you tidy the tags and want them side by side in a sheet.
Watch out
the Organization ID is required to run it, and each run costs a task.
60

List SMSFs

Action

In Zapier“List all SMSFs.”

Lists the SMSF clients of the organisation in one step.

When to use it
when an SMSF tracker kept elsewhere should be rebuilt from Nagaris instead of by hand.
Watch out
check at test how the list is returned before mapping it into another app.
61

List Sole Traders

Action

In Zapier“List all sole traders.”

Exports every sole trader client of the organisation into the Zap.

When to use it
when a mailing aimed at sole traders needs the full list.
Watch out
the Organization ID is required, and the step costs a task each time it works.
62

List Trusts

Action

In Zapier“List all trusts.”

Pulls the full list of trust clients held in the organisation.

When to use it
when your trust register kept outside Nagaris needs a full refresh from the source.
Watch out
each successful run counts as a task like any other action, reads included.
63

Get Partnership

Action

In Zapier“Get a partnership by id.”

Reads one partnership client so its details can feed the steps that come after it.

When to use it
when an update in another app needs the current partnership details first.
Watch out
needs the Client UUID of the partnership, plus the Organisation ID.
64

Get a Client Address

Action

In Zapier“Get a client address by id.”

Tells you which address belongs to which client, one link at a time.

When to use it
when you need to know where a client is based before sending them a letter.
Watch out
needs the Client Address UUID, which is not the same as the Address ID.
65

Get a Client Contact

Action

In Zapier“Get a client contact by id.”

Reads one link between a contact and a client, found by the ID of that link.

When to use it
when you hold a client contact ID and a later step needs what Nagaris keeps on that link.
Watch out
the Client Contact UUID is required, not the plain Contact ID.
66

Get a Client Document

Action

In Zapier“Get a client document by id.”

Reads one client document record by its ID, so the steps that follow can use what Nagaris returns.

When to use it
when you need the details of a document before acting on it.
Watch out
the Client Document UUID is required.
67

Get Client Email

Action

In Zapier“Get a client email by id.”

Turns a client email record ID into the record itself, for the steps that follow.

When to use it
when you hold an email record ID and the next step needs the actual address.
Watch out
the Client Email UUID is required to say which record.
68

Get Client Group

Action

In Zapier“Get a client group by id.”

Fetches a client group by its ID so its details can be reused further down the Zap.

When to use it
when you hold a group ID and the next step needs the group name.
Watch out
the Client Group ID is required.
69

Get Client Group Contact

Action

In Zapier“Get a client group contact by id.”

Checks one contact attached to a client group, found by its ID.

When to use it
when a group contact ID arrives and a later step needs what Nagaris keeps on it.
Watch out
needs the Client Group Contact ID to say which contact.
70

Get a Client Group Document

Action

In Zapier“Get a client group document by id.”

Loads one document held at client group level, by its ID, for the steps that follow.

When to use it
when a group document ID arrives and you need its name for a reminder.
Watch out
the Client Group Document UUID is required.
71

Get Client Note

Action

In Zapier“Get a client note by id.”

Given a note ID, this step brings back the full content of that client note.

When to use it
when you hold a note ID and want the whole text in a chat message.
Watch out
the Client Note UUID is required to say which note.
72

Get a Client Phone

Action

In Zapier“Get a client phone by id.”

Resolves one client phone record from its ID, for the steps that follow.

When to use it
when a call reminder in another tool needs the number behind a phone ID.
Watch out
the Client Phone UUID is required to say which number.
73

Get a Client Service

Action

In Zapier“Get a client service by id.”

Retrieves one service assigned to a client, by the ID of the assignment.

When to use it
when a reminder or an invoice needs the details of a client service.
Watch out
the Client Service UUID is required; check at test which details come back.
74

Get a Client Trustee

Action

In Zapier“Get a client trustee by id.”

Reads one trustee link on a client, found by the ID of that link.

When to use it
when a trust update needs to know who the trustee is before notifying anyone.
Watch out
the Client Trustee UUID is required to say which link.
75

Get a Client Website

Action

In Zapier“Get a client website by id.”

Reads one website stored on a client, so the next step can use the address.

When to use it
when a report or a message needs the site of a business client.
Watch out
the Client Website UUID is required, not the client's own ID.
76

Get a Company

Action

In Zapier“Get a company by id.”

Opens one company client by its ID, so its registrations can be read by the next steps.

When to use it
when a later step needs to know whether a company is registered for GST or payroll tax.
Watch out
needs the Client UUID of the company, filled in from an earlier step.
77

Get a Contact

Action

In Zapier“Get a contact by id.”

Looks up one contact by its ID and passes the person's details to the steps that follow.

When to use it
when you hold a contact ID and want the person's name and details for a message.
Watch out
needs the Contact ID, so check at test that the right person comes back.
78

Get a Handover

Action

In Zapier“Get a handover by id.”

Fetches one handover by its ID for the steps that follow.

When to use it
when a handover should be forwarded to someone who works outside Nagaris, by email or in a team chat.
Watch out
the Handover UUID is required to say which handover.
79

Get Individual

Action

In Zapier“Get an individual by id.”

Retrieves an individual client by its ID, so a later step can use the details Nagaris returns.

When to use it
when an earlier step tells you which client, and you need the person's name for an email.
Watch out
the Client UUID is required, and it has to be the ID of an individual.
80

Get Organisation

Action

In Zapier“Get an organisation by id.”

Reads one organisation by its ID and hands its details to the next steps.

When to use it
when a later step needs the organisation name and you only have the ID.
Watch out
a Get action is still an action, so it counts as a task when it succeeds.
81

Get Other Entity

Action

In Zapier“Get an other entity by id.”

Picks up one client of the other entity type by its ID.

When to use it
when a client of that type needs its details pulled into another tool.
Watch out
needs the Client UUID, even though the record is called an other entity.
82

Get a Package

Action

In Zapier“Get a package by id.”

Reads one package by its ID, for the steps that follow.

When to use it
when an invoice step in another app needs the package amount.
Watch out
the Package ID is required, so check at test that the right package comes back.
83

Get a Service

Action

In Zapier“Get a service by id.”

With a service ID in hand, this step reads that service entry for the rest of the Zap.

When to use it
when a later step needs the details of a service.
Watch out
the Service ID is required, so check at test that the right service comes back.
84

Get Service Tag

Action

In Zapier“Get a service tag by id.”

Reads one service tag by its ID so its name can be reused.

When to use it
when a report needs the name behind a tag ID.
Watch out
the field asked for is the Service UUID, so check at test that the tag comes back.
85

Get SMSF

Action

In Zapier“Get a smsf by id.”

Grabs one SMSF client by its ID, with the details Nagaris returns for it.

When to use it
when you hold an SMSF ID and the next step needs its name.
Watch out
the SMSF UUID is required, so check at test that the right record comes back.
86

Get Sole Trader

Action

In Zapier“Get a sole trader by id.”

Shows one sole trader client to the rest of the Zap, found by its ID.

When to use it
when you hold a client ID and need the trader's name.
Watch out
the field is labelled Solo Trader UUID, not Sole Trader, so look for that spelling.
87

Get Trust

Action

In Zapier“Get a trust by id.”

Loads one trust by its ID so its details are available to the steps that follow.

When to use it
when a message about a trust needs its name.
Watch out
the Trust UUID is required, so check at test that the right trust comes back.
88

List Organisations

Action

In Zapier“List all organisations.”

Pulls the organisations the connected account can see, in one step.

When to use it
when you want to see which organisations the account reaches before you fill in the Organisation ID of your other steps.
Watch out
no required field is listed for it, so check at test what comes back.
89

List Client Contacts

Action

In Zapier“List client contacts.”

Returns the client contact links across the organisation, so you see who is attached to which client.

When to use it
when a sheet should show who speaks for which client.
Watch out
the Organization ID is required to run it.
90

List Client Documents

Action

In Zapier“List client documents.”

All the client document records of the organisation, requested or not, land in the Zap with this step.

When to use it
when a tracker of outstanding papers is rebuilt from Nagaris.
Watch out
the Organization ID is required to run it, and the step costs a task.
91

List Client Emails

Action

In Zapier“List client emails.”

Every client email record of the organisation comes back from this step in one go.

When to use it
when an email tool should be rebuilt from the addresses held in Nagaris.
Watch out
check at test what the list holds before mapping it, and remember the run costs a task.
92

List Client Groups

Action

In Zapier“List all client groups.”

Returns all client groups of an organisation in one go.

When to use it
when a report built in another app needs the full group list.
Watch out
check at test what comes back before mapping a whole list into one field.
93

List Client Notes

Action

In Zapier“List client notes.”

Returns every client note of the organisation in one step.

When to use it
when notes should be archived in a document tool outside Nagaris.
Watch out
check at test what comes back before mapping it, a long list can be hard to place.
94

List Client Phones

Action

In Zapier“List client phones.”

Dumps the client phone records of the organisation into the Zap in one go.

When to use it
when a calling tool should receive the whole phone directory of the firm.
Watch out
the Organization ID is required to run this step.
95

List Client Services

Action

In Zapier“List client services.”

Shows which services are assigned to which clients across the organisation.

When to use it
when you want to see who receives what before a run of invoices.
Watch out
check at test what the list returns before mapping it.
96

List Client Trustees

Action

In Zapier“List client trustees.”

Returns the trustee links held across clients of the organisation.

When to use it
when a review kept in a spreadsheet needs every trustee on file.
Watch out
the Organization ID is required to run it, and the step counts as a task.
97

List Client Websites

Action

In Zapier“List client websites.”

Returns the website records stored across clients of the organisation.

When to use it
when you check which business clients still have no site on file.
Watch out
each successful run costs a task, and the Organization ID is required.
98

List Client Addresses

Action

In Zapier“List client addresses.”

Returns client address links rather than loose address records.

When to use it
when a postal run should only cover addresses tied to clients.
Watch out
the Organization ID is required, and a step after it makes the Zap multi-step.
99

List Client Group Documents

Action

In Zapier“List all client group documents.”

Collects every document held at client group level in the organisation.

When to use it
when you check which group papers are still requested, without opening each client group in Nagaris.
Watch out
each successful run is a task, and the Organization ID is required.
100

Update Client Address

Action

In Zapier“Updates a client address.”

Points a client address link at a different address or a different client.

When to use it
when a client moves and the new address record already exists in Nagaris.
Watch out
the Client Address UUID, Address UUID and Client UUID are all required.
101

Update Client Contact

Action

In Zapier“Updates a client contact.”

Changes the link between a contact and a client, for example to make it the primary one.

When to use it
when the main contact of a client changes and the record should show the new one.
Watch out
needs the Client Contact UUID on top of the contact and client UUIDs.
102

Update Client Document

Action

In Zapier“Updates a client document.”

Renames a client document entry or changes its requested state, so the file shows where each paper stands.

When to use it
when a paper arrives through another tool and the request on the client should be marked accordingly.
Watch out
the Client Document UUID and the Client UUID are both required to say which document.
103

Update Client Email

Action

In Zapier“Updates client email.”

Corrects an email address already stored on a client, or its primary flag.

When to use it
when a bounce in your mailing tool tells you the address on file is wrong.
Watch out
needs the Client Email UUID, so the Zap must know which email record to change.
104

Update Client Group

Action

In Zapier“Updates a client group in the system.”

Edits a client group: its name, its prospect flag or its finalised state.

When to use it
when a deal marked won in your CRM should mark the group as no longer a prospect.
Watch out
the Client Group ID must be filled in, so the Zap knows which group to change.
105

Update Client Group Contact

Action

In Zapier“updates a client group contact.”

Adjusts a contact attached to a client group, including whether the client can see or edit it.

When to use it
when access granted in a client portal should be mirrored in Nagaris.
Watch out
the Client Group Contact ID is required.
106

Update Client Group Document

Action

In Zapier“Updates a client group document.”

Changes a document entry held at client group level: its name or whether it is still requested.

When to use it
when a group-wide paper has been received and should no longer show as requested in Nagaris.
Watch out
needs the Client Group Document UUID and the Client Group UUID, taken from an earlier step.
107

Update Client Phone

Action

In Zapier“Updates a client phone.”

Replaces a phone number on a client with the one you map in.

When to use it
when a number confirmed in another tool should overwrite the one in Nagaris.
Watch out
the Client Phone UUID identifies the number and is required.
108

Update Client Service

Action

In Zapier“Updates a client service.”

Changes a service assigned to a client, including the date it starts.

When to use it
when an engagement start is moved and the client service should follow.
Watch out
Start Date stays required even when you only change something else.
109

Update Client Trustee

Action

In Zapier“Updates a client trustee.”

Repoints the trustee record linked to a client.

When to use it
when a trustee is replaced and the link must point to the new person.
Watch out
the Client Trustee UUID, Client UUID and Trustee UUID are all required.
110

Update Client Website

Action

In Zapier“Updates a client website.”

Swaps the website stored on a client for a new address, and can change which site counts as primary.

When to use it
when a business client moves to a new domain and tells you through a form or an email.
Watch out
needs the Client Website UUID as well as the new Website URL, so the Zap must know which record to touch.
111

Update a Company

Action

In Zapier“Updates a company by id.”

Changes a company client, from its name to registrations like FBT, PAYG or fuel tax credits.

When to use it
when a registration confirmed elsewhere should be ticked on the company.
Watch out
the Client UUID identifies the company and is required.
112

Update Contact

Action

In Zapier“Updates a contact by id.”

Rewrites the details of a contact already held in the Nagaris contact list.

When to use it
when a person updates their details in a form and Nagaris should hold the new version.
Watch out
needs the Contact ID, so put a step before it that provides one.
113

Update Individual

Action

In Zapier“Updates an individual.”

Modifies an individual client, including the flag for tax residency.

When to use it
when a change of situation recorded in an intake tool should reach the client record.
Watch out
Client UUID, Contact UUID, Client Group UUID and Client Name are all required.
114

Update Organisation

Action

In Zapier“Updates an organisation.”

Changes the name of an organisation in Nagaris, the only field it asks for besides the Organisation ID.

When to use it
when a rebrand recorded elsewhere should be reflected at the top level of Nagaris.
Watch out
the Organisation ID identifies which one to change, so map it from an earlier step.
115

Update Other Entity

Action

In Zapier“Updates an other entity.”

Alters a client of the other entity type with the values mapped into it.

When to use it
when an unusual structure needs a migration flag set after review.
Watch out
the same four identifiers as the other client types are required.
116

Update a Package

Action

In Zapier“Updates a package in the system.”

Edits a package already attached to a client group: its name, its amount, its group or its active state.

When to use it
when a fee revision approved in your quoting tool should update the package on file.
Watch out
Package Id, Name, Amount and Client Group UUID are all required, so map each one.
117

Update Partnership

Action

In Zapier“Updates a partnership.”

Modifies a partnership client already in Nagaris, such as its clean-up or migration flags.

When to use it
when a partnership clean-up flag should be set from a review sheet.
Watch out
Client UUID, Client Group UUID and Client Name are required each time.
118

Update a Service

Action

In Zapier“Updates a service.”

Modifies a service in the catalogue: name, active state or billable state.

When to use it
when a service is retired in your price list and should be switched off in Nagaris.
Watch out
the Service UUID and Service Name are required.
119

Update Service Tag

Action

In Zapier“Updates a service tag by id.”

Renames or deactivates a service tag in Nagaris.

When to use it
when the tagging scheme kept in a spreadsheet changes and Nagaris should match it without manual edits.
Watch out
needs the Service Tag UUID and a Name, even if you only want to switch the tag off.
120

Update SMSF

Action

In Zapier“Updates SMSF by id.”

Applies your changes to an SMSF client found by its ID.

When to use it
when a fund moves group or changes name and your SMSF tracker is the first to know.
Watch out
the Client UUID tells the Zap which fund to change, so fill it in with care.
121

Update Sole Trader

Action

In Zapier“Updates Sole Trader by id.”

Changes a sole trader record by its ID, flags included.

When to use it
when a sole trader is no longer a prospect and the record should catch up.
Watch out
the Client Name is required even if you only change a flag.
122

Update Trust

Action

In Zapier“Updates a trust by id.”

Rewrites a trust client, found by its ID, with the values you map in.

When to use it
when a trust becomes GST registered and the record should say so.
Watch out
Client UUID, Client Group UUID and Client Name are required each time.
123

Create Client Document

Action

In Zapier“Uploads a document to Nagaris for a client.”

Uploads a document to a client in Nagaris under the name you give it, so the file sits with the rest of the record.

When to use it
when signed papers or statements arrive in another tool and should end up on the client file.
Watch out
needs a Client ID and a Document Name; check at test that the file comes through.
When it breaks

When a Nagaris Zap breaks

Nagaris has no limit of its own on file with Zapier, so the cases below are the general ones. They apply to every Nagaris Zap.

If a Zap stops doing what you expect, check these four cases first. For anything else, see our Zapier troubleshooting guide.

  • No catch-up on the past

    A Zap only reacts to what happens after you switch it on. Clients already in Nagaris are never picked up; moving that backlog is a separate job.

  • A Zap that feeds itself

    A Zap that writes where its own trigger looks can set itself off again and again, and burn through the task count. Keep trigger and action on different records.

  • Flood protection on big batches

    After a bulk import, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection.

  • The same item, never twice

    Zapier keeps track of what a polling trigger has already seen, so the same item does not start the Zap twice.
Need help

Need help automating Nagaris with Zapier?

A person reads every message.

FAQ

Nagaris Zapier integration: your questions

01Is the Nagaris Zapier integration free?
Yes, Nagaris is not a premium app, so it works on the free Zapier plan. That plan gives you 100 tasks a month and an unlimited number of Zaps, each limited to two steps: one trigger and one action. Once a Zap needs a second action or a filter, it becomes multi-step and needs a paid plan. Every operation of Nagaris can be used in a two-step Zap, so a simple sync between Nagaris and one other app fits the free plan.
02How many tasks does a Nagaris Zap use?
One task per action that succeeds, nothing for the trigger. Zapier can check Nagaris as often as your plan allows without spending anything; only completed actions are billed. A Zap with a Nagaris trigger and one action uses one task per run, a Zap with three actions uses three. An action that fails is not counted. Keep in mind that the Get and List actions of Nagaris are actions too, so each successful read costs a task like a write does.
03Does Nagaris trigger Zaps in real time?
No. All 42 Nagaris triggers are polling triggers: Zapier asks Nagaris for new items at a fixed interval. That interval depends on your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans the interval can be changed, and a check can also be run by hand from the editor. None of the triggers is instant, so nothing reaches Zapier the moment it happens in Nagaris.
04What does it take to connect Nagaris to Zapier?
An account on Nagaris, plus read or write access on anything you do not own yourself and want the Zap to touch. You add the connection from the Apps page of Zapier, sign in to Nagaris in the tab that opens and grant access. Have the Organisation ID at hand as well: almost every trigger and action asks for it as a required field, and nothing can be tested until it is filled in.
05Why does every Nagaris step ask for an Organisation ID?
Because nearly every Nagaris trigger and action lists it as a required field. The spelling changes with the step: triggers say Organization ID, while most actions say Organisation ID. Keep the value at hand before you build anything, fill it in on each Nagaris step, then run the test and check that real items come back before you publish. On the free plan a Zap holds one trigger and one action, so a Zap between two Nagaris steps asks for it twice, and a Zap with one other app asks for it once.
06What if a Nagaris operation is missing from Zapier?
Then this integration cannot do it, whatever Zap you build. The Nagaris page on Zapier shows the current list of triggers and actions, so check it before you plan a workflow. Know that nothing on that list searches: there is no search step, and each Get action reads one record by its ID, so a lookup by name is out of reach. The List actions bring back a whole set instead, and each successful run costs a task. If the job needs a second action in the same Zap, that makes it multi-step, which needs a paid plan.
07Zapier, Make or n8n for Nagaris?
It depends on a few criteria rather than a winner. First, availability: Nagaris has 165 operations on Zapier, so check whether the other tool offers the ones your workflow needs. Second, timing: all Nagaris triggers on Zapier are polling, so the interval of your plan sets how fast data moves. Third, volume: Zapier bills each successful action as a task, which matters if you read and write many records per run.
Same platform

Other docs you might need on this stack.

Browse all integrations