Avaza
Project ManagementAvaza is an all-in-one suite for project management, resource scheduling, timesheets, expenses, quoting and invoicing. Agents create projects and tasks, log time and expenses, issue estimates and invoices, and start flows the moment Avaza records change.
What This Integration Enables
Most project tools stop at the task. Avaza does not: the same API that holds a project's tasks also holds its timesheets, its expenses, its estimates, its invoices, its payments and its supplier bills. That matters more than the operation count suggests, because it means the moment an hour becomes billable is an API call rather than an export into an accounting system. An agent that can read a project's budget, aggregate the hours booked against it and raise the invoice is working inside one boundary rather than reconciling across three.
FlowRunner agents run that whole chain. They open projects and sections from won deals, book people onto them with schedule bookings, log time and expenses from wherever the work was actually recorded, aggregate hours per project on a schedule, and raise estimates and invoices when the milestone is met. The automation exceptions show up exactly where you would expect: an hour booked to the wrong project, an expense with no receipt, a budget crossed mid engagement. Those go to a person. Every action is built and verified against the Avaza API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
A won deal becomes a staffed project
A deal closes in HubSpot. The agent resolves or creates the customer with Create Company, then calls Create Project with the billing type and budget the deal implies. Because a task in Avaza cannot exist outside a section, Create Section runs first and Create Task fills the plan from the statement of work. Add Project Member puts the delivery team on with their rates and budgets, and Assign Project Timesheet Category sets which categories are billable and at what rate before anyone logs an hour against them. Create Schedule Booking reserves the people for the dates. A kickoff summary posts to Slack with the project and its budget named.
-
Budget drift caught while the engagement is still live
On a schedule, the agent calls Get Timesheet Summary grouped by project and person, and compares it to the budgets on List Projects. Projects past a threshold post to the delivery lead with the breakdown attached: which category consumed the budget, who booked the hours, and how much of the plan remains on List Tasks. Where the engagement is fixed fee, the agent reads List Fixed Amounts to see what has already been billed against it. Nobody discovers an overrun in the month end review, because the signal arrives while there is still scope to renegotiate.
-
Milestone to invoice, with the accounting system kept in step
A milestone task closes. The agent gathers the approved time and chargeable expenses for that milestone from List Timesheets and List Expenses, builds the lines, and calls Create Invoice as a draft. Get Invoice returns the shareable link, which posts to the account owner for review. Once the invoice is issued, the same figures reconcile into Xero or QuickBooks Online, and when the customer pays through Stripe the agent records it with Create Payment and allocates it against the invoice so the receivables ledger and Avaza agree without anyone typing twice.
Human-in-Loop Highlight
Reject Timesheets is not a state change, it is a message. Rejecting a batch emails every affected person by default, so the agent that rejects an entry has told a named colleague their week was wrong. It also has a closing window: Avaza refuses to reject entries that have already been invoiced or paid, which means the last honest moment to dispute an hour is before the invoice run, not after it. So the reconciliation agent approves what reconciles and stops on what does not. It posts: "Four entries fail the scope check before Friday's invoice run. Three are 11.5 hours booked by Dana to Harbour Redesign under Strategy, a category that project bills at zero. One is a 6 hour entry with no task. Rejecting mails each person. Reject all four, reject only Dana's, or approve as booked?" The lead answers once. The agent runs Reject Timesheets on exactly that set and Approve Timesheets on the rest. What the agent contributed was the reconciliation. What it declined to do was tell somebody their timesheet was wrong on its own authority.
Agent Capabilities
101 actionsAccount Reference Data
11- Get Account Retrieves the account's configuration, including timesheet settings, default currency and feature flags. Read first when a flow needs to know how the account is set up before writing.
- List Currencies Retrieves the currency reference table with each currency's code, symbol and decimal places.
- List Taxes Retrieves the tax rates configured in the account, including the components of compound taxes. Invoice and bill lines reference these.
- List Task Statuses Retrieves the task status definitions, grouped by task type, including which statuses count as complete. Status codes are per account, so flows read them rather than assuming.
- List Task Priorities Retrieves the task priority definitions with their codes, colors and display order.
- List Task Types Retrieves the task type definitions, which are Avaza's workflows. Each type carries its own set of statuses.
- List Project Tags Retrieves every project tag in the account, whether or not it is currently in use.
- List Expense Categories Retrieves the expense categories configured in the account, including any per-unit pricing used for mileage-style expenses.
- List Expense Payment Methods Retrieves the expense payment methods configured in the account, such as company card or personal funds.
- Lookup Expense Groups Searches the expense group and trip names used to bundle expenses into a single report.
- Lookup Expense Merchants Searches the merchant names already used on expenses, which is what keeps a coding flow consistent with history.
Users
4- List Users Retrieves the people who hold a role in the account, filterable by role, tag, company or email address.
- Create User Creates a user. Supplying a company makes them a customer contact and leaving it empty makes them a team member. Enabling the invite email delivers a real invitation, and a paid role can consume a billable seat.
- Update User Updates a user. Only the fields supplied are written. Supplying roles replaces the whole role set rather than adding to it.
- Set User Archived Archives a user or brings them back. Archiving deletes every role assignment and disables project memberships, and unarchiving restores neither, so a leaver flow records what it removed.
Companies and Contacts
7- List Companies Retrieves the customer companies with their contacts, billing address and financial settings. Filter by updated date to sync only what has changed.
- Get Company Retrieves one customer company by id, including its contacts and billing address.
- Create Company Creates a customer company. Projects, invoices and expenses all hang off a company, so this is usually the first write in a new client flow.
- Update Company Updates a customer company, writing only the fields supplied.
- List Contacts Retrieves the external customer contacts, optionally narrowed to one company.
- Get Contact Retrieves one external contact by id.
- Create Contact Creates an external customer contact. Supplying a company name that matches nothing creates a new company as a side effect, so flows pass an id when they mean an existing one.
Projects
10- List Projects Retrieves projects with their status, billing type, budget and dates. The widest filter set in the API, so flows filter here rather than reading everything.
- Get Project Retrieves one project in full, including its sections, its members with their rates and permissions, and its tags.
- Create Project Creates a project under a customer company. Used to turn a won deal into a staffed engagement in one step.
- Update Project Updates a project, writing only the fields supplied. Supplying project tags replaces the whole tag set.
- Lookup Projects Searches active projects grouped by customer company, which is cheaper than a full listing when all a flow needs is a name and an id.
- List Project Members Retrieves project members with their rates, budgets and permissions. Requires a project, a user, or both.
- Add Project Member Adds a user to a project with their rates, budget and task permissions. Rates left empty fall back to the user's own defaults.
- Update Project Member Changes a project member's rates, budget or permissions, writing only the fields supplied.
- List Project Timesheet Categories Retrieves the timesheet and billing categories assigned to projects, with their rates and hour budgets.
- Assign Project Timesheet Category Assigns a timesheet category to a project, or updates the assignment, setting its billable flag, rate and hour budget. This is what decides whether an hour booked to it is worth anything.
Sections
3- List Sections Retrieves the sections of a project. A section is Avaza's task group, and every task must live in one.
- Create Section Creates a section in a project. Run before creating tasks, because a task cannot exist outside a section.
- Delete Section Deletes a section. Avaza refuses while it still contains tasks.
Tasks
9- List Tasks Retrieves tasks with their assignees, dates, status, priority, tags and tracked time. Filter by parent task to walk the subtask hierarchy a layer at a time.
- Get Task Retrieves one task in full, including its project and section.
- Create Task Creates a task. Both a project and a section are required, and setting a parent task creates a subtask instead of a top level one.
- Update Task Updates a task, writing only the fields supplied. Supplying tags replaces the whole tag set, while file attachments add to the existing ones.
- Delete Task Permanently deletes a task, applying the same rules the Avaza web app applies.
- Lookup Tasks Searches a project's tasks grouped by section. The search matches from the beginning of the name, so a middle word will not find anything.
- List Task Comments Retrieves the discussion on a task, including replies, attachments and Avaza's own system messages.
- Create Task Comment Posts a comment to a task, optionally as an internal note or as a reply. An internal note stays hidden from external and customer users.
- Update Task Comment Rewrites a comment the connected user authored. Attachments left out of the update are removed, and edits are silent.
Timesheets
12- List Timesheets Retrieves timesheet entries with filters for date range, user, project, task, category, billable and invoiced state, approval status and running timers. The read a billing reconciliation starts from.
- Get Timesheet Retrieves one timesheet entry, including its approval state and timer details.
- Create Timesheet Logs time against a project in decimal hours. Leaving the duration empty starts a running timer rather than creating an empty entry.
- Update Timesheet Updates a timesheet entry, writing only the fields supplied. Avaza requires the project on every update even when it is not what is changing.
- Delete Timesheet Permanently deletes a timesheet entry. The hours come off every total that included them.
- List Deleted Timesheets Retrieves the tombstones of deleted timesheet entries, so a downstream copy can be kept in step.
- Get Timesheet Summary Aggregates tracked hours over a date range, grouped by up to three dimensions such as project, user, category or month. The read behind a budget check.
- Submit Timesheets Submits a whole day or a whole week of draft time for approval. This emails the approvers unless notifications are turned off.
- Approve Timesheets Approves a batch of pending timesheet entries, between one and five hundred at a time. Entries the connection may not approve come back marked individually rather than failing the batch.
- Reject Timesheets Rejects a batch of pending or approved timesheet entries. This emails every affected person by default, and entries already invoiced or paid cannot be rejected, which is why the human gate on this page sits here.
- Get Running Timer Reports whether a timer is running, when it started and which entry it belongs to.
- Set Timer Running Starts or stops the timer on a timesheet entry. Stopping adds the elapsed time to the entry's duration.
Expenses
7- List Expenses Retrieves expense entries with filters for date range, person, project, category, chargeable and invoiced state, approval status and merchant.
- Get Expense Retrieves one expense entry, including its category, project, tax, attachment and approval details.
- Create Expense Records an expense. Supplying a category, tax or trip by name rather than by id creates a new one when nothing matches, so flows pass ids when they mean existing records.
- Update Expense Updates an expense, writing only the fields supplied.
- Delete Expenses Deletes one or more expenses in a single call. Each comes back marked individually, so a partial failure is visible rather than silent.
- Submit Expenses For Approval Submits a person's draft expenses for approval. This emails the approvers unless notifications are turned off.
- Get Expense Summary Aggregates expense amounts over a date range, grouped by up to three dimensions such as category, project, user or month.
Schedule
8- List Schedule Series Retrieves scheduled work bookings and leave, filterable by date range, person, project, category and leave type.
- Find Schedule Series Retrieves specific schedule series by their identifiers, which the query-string listing cannot do.
- List Schedule Assignments Retrieves the individual scheduled days that make up bookings, for day-by-day allocation rather than the booking as a whole.
- Create Schedule Booking Books a person onto a project over a date range, with hours given either per working day or spread across the range.
- Update Schedule Booking Changes an existing project booking. This route takes the whole booking as it should end up rather than a field list.
- Create Schedule Leave Books time off for a person over a date range. Enabling notification sends a real email about the leave.
- Update Schedule Leave Changes an existing leave booking.
- Delete Schedule Series Deletes a booking or a leave entry along with every scheduled day it created.
Files
2- Upload File From URL Uploads a file by handing Avaza a public address to fetch it from, optionally linking it to a task, expense, estimate or invoice in the same call.
- Upload File From Base64 Uploads a file supplied as base64 text, optionally linking it to a task, expense, estimate or invoice. Used when the bytes are already in hand.
Invoicing
8- List Invoices Retrieves customer invoices with their line items, addresses and status.
- Get Invoice Retrieves one invoice by its transaction id, including line items and its shareable web links.
- Create Invoice Creates a draft invoice with its line items. The write at the end of a milestone-to-billing flow.
- Update Invoice Updates a draft invoice, writing only the fields supplied. Supplying line items deletes every existing line left out, so flows send the whole set.
- List Recurring Invoices Retrieves the recurring invoice profiles, including their schedule and the date the next invoice is due.
- Get Recurring Invoice Retrieves one recurring invoice profile, including its line items and schedule.
- List Credit Notes Retrieves customer credit notes, including their line items and how they are allocated against invoices.
- Get Credit Note Retrieves one credit note, including its line items and invoice allocations.
Estimates
4- List Estimates Retrieves quotes and estimates with their line items and status.
- Get Estimate Retrieves one estimate, including its line items, parties and shareable web links.
- Create Estimate Creates a draft estimate with its line items, which is how a scoped proposal reaches the client.
- Update Estimate Updates an estimate, writing only the fields supplied. Supplying line items deletes every existing line left out.
Payments
3- List Payments Retrieves customer payments with the invoices each one is allocated against.
- Get Payment Retrieves one customer payment, including how it is allocated across invoices.
- Create Payment Records a customer payment and optionally applies it to specific invoices. The allocations must add up to the payment amount.
Bills
6- List Bills Retrieves supplier bills with their line items, status and addresses.
- Get Bill Retrieves one supplier bill, including its line items and web links.
- Create Bill Creates a draft supplier bill with its line items, which is how subcontractor cost reaches the project it belongs to.
- List Bill Payments Retrieves supplier bill payments with the bills each one is applied against.
- Get Bill Payment Retrieves one supplier bill payment, including its allocations to bills.
- Create Bill Payment Records a payment to a supplier and optionally applies it to specific bills.
Inventory
3- List Inventory Items Retrieves the products and services configured in the account, which are what line items reference.
- Get Inventory Item Retrieves one product or service by its id.
- List Fixed Amounts Retrieves the fixed-price billing entries used to invoice fixed-fee work, filterable by project, task and invoiced state.
Webhooks
4- List Webhooks Retrieves the account's active webhook subscriptions, each with its event code and callback address. Used to find a stale subscription.
- Get Webhook Retrieves one webhook subscription by its identifier.
- Create Webhook Subscribes an address to one event. A subscription covers a single event, so watching several means creating several.
- Delete Webhook Removes a webhook subscription, either by identifier or by callback address. Deleting by address removes every subscription pointing at it.
Triggers
1 triggersEvent Triggers
1- On Account Event Fires when the selected event happens anywhere in the Avaza account, with any event delivering all of the account's event types through one trigger. One behavior is worth designing around: Avaza's own write operations do not fire their events unless the account has webhook sending turned on, so a change this connector makes is invisible to this trigger by default. That is a useful default rather than a limitation, because it stops a flow reacting to its own writes, but a flow that genuinely needs to see them has to enable it deliberately.
Frequently Asked Questions
What can FlowRunner do with Avaza?
FlowRunner agents can run Get Account, List Currencies, and List Taxes in Avaza, plus 98 more actions.
Does connecting Avaza to FlowRunner require OAuth?
No. Avaza connects to FlowRunner with an API key, no OAuth flow required.
Can Avaza trigger a FlowRunner workflow automatically?
Yes. Avaza supports 1 trigger that can start a FlowRunner workflow automatically.
Other Project Management integrations
Start building with Avaza
Free plan, no card required. Connect in minutes.