Avaza Zapier integrationAutomate Avaza with Zapier.

Drafts a quote in Avaza from data that arrived elsewhere, such as a scoping form. The quote then lives in Avaza like any other, ready for someone to review before it goes out.

Sets up a project in Avaza, with options such as timesheet approval or default members. It's the usual first action when a deal closes somewhere else and work needs a home in Avaza.

Puts a task in a given project and section, with its title. The task then shows up for the team like any other, ready for time to be logged against it.

Adds a supplier bill to Avaza from another source. It keeps supplier costs inside Avaza next to the project they belong to, instead of in a separate inbox.

Marks a payment made against a bill, closing the loop on what you owe. It's the payables twin of Create Invoice Payment, and it keeps what you owe and what you've paid in one place.

Opens a new client company in Avaza. Only the company name is required. It's the base record that projects, contacts and invoices attach to later on.

Logs a new expense in Avaza with its date and whether it's chargeable or reimbursable. It saves consultants from typing the same receipt twice, once in the capture app and once in Avaza.

Records money received against an invoice, so Avaza knows it's paid. It saves a manual reconciliation step that is easy to forget at the end of a busy month.

Staffs a project with a colleague and sets what they can do: log time, approve, handle tasks. Permissions such as approving timesheets or expenses, or creating and deleting tasks, are set in the same step.

Creates a category people pick when logging time on a project, flagged billable or payable. Setting it by Zap means every new project starts with the same categories instead of a hand-made list.

Books a person's time in the resource schedule, with an option for days off. It fills the resource calendar from outside Avaza, so planning reflects what was promised to clients.

Puts leave on the schedule so nobody books that person by mistake. It keeps absences visible in the same calendar where bookings are made.

Adds a section, the grouping that holds tasks, inside a project. Sections are what Create Task needs, so this action often runs just before it in the same Zap.

Logs time in Avaza on someone's behalf, with or without start and end times. It's handy when time is already measured in another tool and nobody wants to log it twice.

Removes an expense, chosen by its Expense ID. A filter before this step is worth it if the source is noisy, so only the right claims get deleted.

Removes a whole booking or leave series from the schedule, by its Schedule Series ID. The same action handles bookings and leave, since Avaza stores both as series.

Takes a section out of a project, by its Section ID. The Section ID usually comes from an earlier step, since nobody types IDs into a Zap by hand.

Deletes one task, identified by its Task ID. Without a Task ID from a trigger or from Lookup Task, the step has nothing to act on.

Halts a running timer, chosen by its Timesheet Timer ID. Despite the name, it targets a running timer; saved entries go through Delete Timesheet.

Removes a timesheet entry by its Timesheet Id. Mind the near-twin Stop Timer, which works on a running timer rather than on a saved entry.

Fetches an expense category by its name. It saves you from hard-coding a category ID that might change later.

Finds a project by its name and hands its details to the next steps. It sits among the actions in the editor, not under the search heading, but it plays the same role.

Finds an Avaza user by name. It's what lets a Zap assign people by name instead of by internal ID.

Adds a person to Avaza with first name, last name, email and company, all four required. It's the quickest way to keep client stakeholders in Avaza in step with a form or a CRM.

Produces an invoice in Avaza, line amounts included, without anyone opening the billing screen.

Finds a timesheet category within a project. Project ID and category are both required. It returns the category so the next step can reuse it without anyone looking it up in Avaza.

Lists the comments of a task, given its Task ID. The typo in the name is Zapier's. It returns the whole comment thread, which a later step can send or store.

Gets expenses between a start and an end date, both required. Optional filters narrow it to chargeable or invoiced expenses, which keeps re-billing lists short. It spares someone a manual export.

Looks up fixed amounts by date, optionally only the invoiced ones, and returns them to the Zap. It completes Search Timesheets when a project mixes hourly work and flat fees.

Finds invoices by search criteria and returns them to the Zap. It sits among the actions rather than under the search heading, which surprises people the first time.

Searches projects by criteria, with an option to include archived ones. Archived projects stay out unless you switch that option on, which matters for old engagements.

Reads the resource schedule between two required dates. Both dates are required, and the result covers bookings across the team for that window. It answers the question who is free, and when, without opening the planning screen.

Looks across tasks by criteria. An optional filter keeps only open ones, or only completed ones. It returns matching tasks to the Zap, so a later step can send them on or act on each one.

Pulls timesheet entries between two required dates, with filters such as billable or invoiced. Other filters include whether a timer is running and whether to bring invoice details along.

Finds a task by name inside a given project. Project ID is required. It's the bridge between what a human calls a task and what Avaza needs to update it.

Changes a task found by its Task ID. It's the action most Zaps reach for when an outside event should move work forward in Avaza.

Rewrites the details of a company already in Avaza, located by its ID. It changes what's already there rather than creating a new record, so the client history stays in one place.

Edits an expense identified by its ID. The Expense ID is required, so the Zap needs it from a trigger or a search before this step.

Changes an existing invoice, picked by its ID through the Transaction ID field. The ID usually comes from Search Invoice or from an invoice trigger earlier in the Zap.

Modifies an existing project by its ID, including whether time entries need a task. Project ID is required, and timesheet approval for new members can be switched in the same step.

Adjusts what someone is allowed to do on a project. Project ID and User ID are required. It takes the same permission options as Create Project Member, applied to someone already on the project.

Edits a timesheet category on a project: billable or not, payable or not. It works on a category that already exists, unlike Create Project Timesheet Category.

Moves or reshapes a booking already on the schedule. Like the create action, it offers an option to schedule on days off.

Changes leave already on the schedule. The editor really writes it with an s. It keeps the leave calendar in Avaza aligned with wherever absences are approved.

Corrects logged time, located by its entry ID together with its project ID. Both IDs are required, which usually means a trigger or Search Timesheets runs earlier in the Zap.

Attaches a file, usually a receipt, to an expense in Avaza. It keeps the proof attached to the expense where an approver will look for it.