Plan bookings in a Google Sheet and let Zapier put them on Avaza's Team Schedule. Each new row becomes one booking: a person, a project, dates and hours. For Zapier basics, see connecting Avaza to other apps with Zapier.
Before you start
- A Zapier account. This Zap has search steps, so it needs a paid Zapier plan. The free plan runs two-step Zaps only (see "On Zapier's free plan" below).
- The right Avaza login. Zapier works as the person who connects Avaza, so use an Administrator's login. A Scheduling Manager can only book on projects they're a member of, and their role doesn't include the lookups the search steps use.
- The Team Schedule module is on, in Settings › General. See general settings.
- Everyone you book has the Scheduling User role and is a member of the project. See managing users and contacts.
Set up the sheet
Use a header row, then one row per booking:
Project | Category | Task | Start | End | Hours per day | Notes | |
|---|---|---|---|---|---|---|---|
Marketing Campaign | Design | Write email sequence | 2026-09-21 | 2026-09-25 | 4 | First draft |
- Email: the person's email address in Avaza.
- Project, Category and Task: names exactly as Avaza shows them. The category must be one of the project's timesheet categories. The task is optional.
- Start and End: type dates as YYYY-MM-DD, so the day and month can't be mixed up.
- Hours per day: up to 24, and decimals such as 7.5 are fine. You can use a total hours column instead.
Build the Zap
In Zapier, create a Zap with the trigger Google Sheets, New Spreadsheet Row. Choose the spreadsheet and the worksheet, then test the trigger so Zapier fetches a sample row.
Find the project: Avaza, Search Project, with the Project column. The first time, Zapier asks you to sign in to Avaza: check what it will be able to do, and click Grant Access to Avaza.
Add a Filter step that only continues if step 2 found a project ID.
Find the category. Add the Avaza search for a project's timesheet categories, with the project ID from step 2 and the Category column.
Find the task (optional): Avaza, Search Task, with the project ID from step 2 and the Task column. Add another Filter step if a missing task should stop the Zap.
Find the person: Avaza, Lookup User, with the Email column.
Create the booking: Avaza, Create Schedule Booking. Map the fields as below, then test the step and publish the Zap.
Map the booking fields
Avaza needs its own ID numbers for the person, project, category and task, so map them from the search steps. Zapier's labels may differ slightly.
Field | Required | What to map |
|---|---|---|
Person | Yes | The user ID from Lookup User |
Project | Yes | The project ID from Search Project |
Timesheet category | Yes | The category ID from the category search. Disabled categories are refused. |
Task | No | The task ID from Search Task |
Start date, end date | Yes | The Start and End columns. The end can't be before the start. |
Duration type | Yes | Hours per Day or Total Hours |
Hours per day or total hours | Yes | A number. Hours per day can't be more than 24. Total hours are spread evenly over the booked days. |
Schedule on days off | No | Turn it on to book weekends and holidays too |
Start time | No | A time of day, such as 09:00. The end time is the start time plus the hours per day. |
Notes | No | The Notes column |
Avaza checks the booking as it does in the app:
- The person needs the Scheduling User role and must be an active member of the project.
- A booking can't start or end on the person's day off unless schedule on days off is on. Days off are the days left empty in the person's Standard Working hours (in Contacts), and the holidays in Settings › Scheduling Settings. See scheduling settings.
- If the booking is a task's only booking and the task has one assignee, the task takes the booking's person and dates. See linking schedule bookings to tasks.
On Zapier's free plan
A two-step Zap has no room for searches, so each row must hold Avaza's ID numbers, or you type fixed IDs into the booking step. A project's ID follows /project/view/ in the address bar when the project is open, and a task's ID follows task= when the task is open. People and category IDs aren't shown in the app.
Test the Zap
Add a row to the sheet with real names and dates.
Wait for Zapier. Zaps that start in Google Sheets run on Zapier's schedule for that trigger, so it isn't instant. If a step fails, the Zap's run in Zapier shows the error.
Open Team Schedule in Avaza and find the person on the booking's dates. Check the project, the dates and the hours per day.

If a booking isn't created
Error or problem | What to do |
|---|---|
You don't have permission to Manage the Schedule | Reconnect Avaza in Zapier with an Administrator or Scheduling Manager login. |
Your user account does not have the required roles to use this API endpoint. | A search step failed because the connected login's role can't look that up. Reconnect Avaza with an Administrator login. |
As a Schedule Manager, but not an Admin, you need to be a member of a project… | Add the connected person to the project, or connect as an Administrator. |
This user does not have the Schedule User role | Give the person the Scheduling User role in Contacts. |
This user is not a member of this project | Add or re-enable them under Members in the project's settings. |
Timesheet Category not found, or This Category is disabled | Map the ID from the category search, and use an active category. |
Booking cannot begin (or end) on a non-working day… | Change the dates, or turn on schedule on days off. |
Invalid Duration Type received. | Choose Hours per Day or Total Hours. |
Object reference not set to an instance of an object. | The person's ID doesn't match anyone in Avaza. Map it from Lookup User. |
Blocked by account API policy | An Administrator has limited API access on the API permissions tab. See the Avaza API. |
A search finds nothing | Check the spelling, and that the connected login can see the project. |
Busy Zaps fail now and then | Avaza limits how often apps can call it. See API rate limits. |
Other ways to create bookings
Book people by hand on the Team Schedule (schedule your team, recurring bookings), or while you create a task (linking bookings to tasks). Developers can create bookings with the Avaza API, and hear about changes through webhooks.