> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FreshBooks Webhook Setup Guide

> Configure FreshBooks to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](https://docs.stackone.com/connectors/freshbooks.md#getting-started) on the FreshBooks connector page.

## How webhooks are set up

StackOne creates and manages the FreshBooks webhook callbacks automatically when the account is connected, one callback per event you enable, and removes them when the account is disconnected. FreshBooks confirms each new callback by sending a verification code to StackOne, which StackOne returns for you, so there is nothing to configure in FreshBooks.

## Available webhook events

The following FreshBooks events can be enabled. Only events selected in StackOne get a callback, so FreshBooks does not deliver events that are not selected. Each event needs the matching read permission on the connected account, such as `user:invoices:read` for invoice events; bill vendor events need `user:bill_vendors:read`.

**1. Invoice events**

Events related to invoices and recurring invoice profiles.

<ul>
  <li>**Invoice Created** (`invoice.create`) — Fired when an invoice is created</li>
  <li>**Invoice Updated** (`invoice.update`) — Fired when an invoice is updated</li>
  <li>**Invoice Deleted** (`invoice.delete`) — Fired when an invoice is deleted</li>
  <li>**Invoice Sent by Email** (`invoice.sendByEmail`) — Fired when an invoice is sent to a client by email</li>
  <li>**Recurring Invoice Profile Created** (`recurring.create`) — Fired when a recurring invoice profile is created</li>
  <li>**Recurring Invoice Profile Updated** (`recurring.update`) — Fired when a recurring invoice profile is updated</li>
  <li>**Recurring Invoice Profile Deleted** (`recurring.delete`) — Fired when a recurring invoice profile is deleted</li>
</ul>

**2. Estimate and credit note events**

Events related to estimates and credit notes issued to clients.

<ul>
  <li>**Estimate Created** (`estimate.create`) — Fired when an estimate is created</li>
  <li>**Estimate Updated** (`estimate.update`) — Fired when an estimate is updated</li>
  <li>**Estimate Deleted** (`estimate.delete`) — Fired when an estimate is deleted</li>
  <li>**Estimate Sent by Email** (`estimate.sendByEmail`) — Fired when an estimate is sent to a client by email</li>
  <li>**Credit Note Created** (`credit_note.create`) — Fired when a credit note is created</li>
  <li>**Credit Note Updated** (`credit_note.update`) — Fired when a credit note is updated</li>
  <li>**Credit Note Deleted** (`credit_note.delete`) — Fired when a credit note is deleted</li>
</ul>

**3. Payment and client events**

Events related to invoice payments and clients.

<ul>
  <li>**Payment Created** (`payment.create`) — Fired when an invoice payment is created</li>
  <li>**Payment Updated** (`payment.update`) — Fired when an invoice payment is updated</li>
  <li>**Payment Deleted** (`payment.delete`) — Fired when an invoice payment is deleted</li>
  <li>**Client Created** (`client.create`) — Fired when a client is created</li>
  <li>**Client Updated** (`client.update`) — Fired when a client is updated</li>
  <li>**Client Deleted** (`client.delete`) — Fired when a client is deleted</li>
</ul>

**4. Expense and bill events**

Events related to expenses, expense categories, vendor bills and bill vendors.

<ul>
  <li>**Expense Created** (`expense.create`) — Fired when an expense is created</li>
  <li>**Expense Updated** (`expense.update`) — Fired when an expense is updated</li>
  <li>**Expense Deleted** (`expense.delete`) — Fired when an expense is deleted</li>
  <li>**Expense Category Created** (`category.create`) — Fired when an expense category is created</li>
  <li>**Expense Category Updated** (`category.update`) — Fired when an expense category is updated</li>
  <li>**Expense Category Deleted** (`category.delete`) — Fired when an expense category is deleted</li>
  <li>**Bill Created** (`bill.create`) — Fired when a vendor bill is created</li>
  <li>**Bill Updated** (`bill.update`) — Fired when a vendor bill is updated</li>
  <li>**Bill Deleted** (`bill.delete`) — Fired when a vendor bill is deleted</li>
  <li>**Bill Vendor Created** (`bill_vendor.create`) — Fired when a bill vendor is created</li>
  <li>**Bill Vendor Updated** (`bill_vendor.update`) — Fired when a bill vendor is updated</li>
  <li>**Bill Vendor Deleted** (`bill_vendor.delete`) — Fired when a bill vendor is deleted</li>
</ul>

**5. Item, service and tax events**

Events related to billable items, services and taxes.

<ul>
  <li>**Item Created** (`item.create`) — Fired when a billable item is created</li>
  <li>**Item Updated** (`item.update`) — Fired when a billable item is updated</li>
  <li>**Item Deleted** (`item.delete`) — Fired when a billable item is deleted</li>
  <li>**Service Created** (`service.create`) — Fired when a service is created</li>
  <li>**Service Updated** (`service.update`) — Fired when a service is updated</li>
  <li>**Service Deleted** (`service.delete`) — Fired when a service is deleted</li>
  <li>**Tax Created** (`tax.create`) — Fired when a tax is created</li>
  <li>**Tax Updated** (`tax.update`) — Fired when a tax is updated</li>
  <li>**Tax Deleted** (`tax.delete`) — Fired when a tax is deleted</li>
</ul>

**6. Project and time tracking events**

Events related to projects and time entries.

<ul>
  <li>**Project Created** (`project.create`) — Fired when a project is created</li>
  <li>**Project Updated** (`project.update`) — Fired when a project is updated</li>
  <li>**Project Deleted** (`project.delete`) — Fired when a project is deleted</li>
  <li>**Time Entry Created** (`time_entry.create`) — Fired when a time entry is created</li>
  <li>**Time Entry Updated** (`time_entry.update`) — Fired when a time entry is updated</li>
  <li>**Time Entry Deleted** (`time_entry.delete`) — Fired when a time entry is deleted</li>
</ul>

## Delivery format

Details of how FreshBooks delivers events to StackOne.

**1. Review the notification fields**

FreshBooks sends each event as a form-encoded POST with `name` (the event, such as `invoice.create`), `object_id` (the record that changed), `account_id`, `business_id` and `identity_id` (the user who made the change). The payload carries no record details, so fetch the record by `object_id` with the matching action, such as getting the invoice for invoice events.

**2. Expect delayed delivery**

FreshBooks does not guarantee delivery timing; events can arrive from seconds to several minutes after the change. Events are sent for changes made in FreshBooks and by other apps using the FreshBooks API. The payload has no event timestamp, so StackOne uses the time the event was received.

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.