Workspace369 n8n integration

The Workspace369 n8n integration works today, on n8n Cloud or your own server. A paid invoice, an accepted proposal or a new lead starts a workflow through the Webhook node, and the HTTP Request node creates or reads clients, invoices, tasks and projects through the Workspace369 API.

Start free trial

14-day free trial. Card required. After the trial: $29/month for Cadet. Renews automatically every month until you cancel. Cancel anytime in Settings → Billing.

Talk to sales
Workflow run
invoice.paidPOST your-n8n.example/webhook/… → 200
HTTP RequestGET mcp.workspace369.com/v1/invoices/{id} → 200
HTTP RequestPOST mcp.workspace369.com/v1/tasks → 200

Workspace369 events in, API calls out

Connected records

Keep client context attached

n8n workflows stay tied to the clients, requests, projects, invoices, payments, files, and activity your team already manages in Workspace369.

Operational fit

Support the work already moving

Use the integration alongside sales, scheduling, delivery, communication, billing, reporting, and accounting instead of treating it as a separate tool.

Team visibility

Give every role the same picture

Help owners, operators, finance, support, and delivery teams understand what happened without stitching together records across disconnected systems.

How it works

How n8n works with Workspace369

  1. 01

    Workspace369 sends the trigger

    In Settings → Webhooks you point events at your n8n Webhook node's production URL. Each event arrives as signed JSON with the record's id.

  2. 02

    n8n runs your workflow

    Nodes use the event's fields, or an HTTP Request node fetches the full invoice, proposal or client from the Workspace369 API first.

  3. 03

    HTTP Request nodes call the API

    The HTTP Request node calls the Workspace369 API over plain HTTPS with your personal access token stored as an n8n credential.

Triggers

The 27 events that can start a workflow

Invoices

invoice.created, invoice.paid (moved into Paid) and invoice.status_changed.

Proposals

proposal.sent, proposal.accepted and proposal.declined.

Contracts

contract.sent, contract.recipient_completed, contract.completed, contract.declined, contract.voided and contract.expired.

Bookings

booking.created, booking.rescheduled, booking.cancelled and booking.no_show.

Clients

client.created and client.stage_changed (moved to another pipeline stage).

Leads

lead.created, lead.converted and lead.archived, for incoming requests.

Time

time_entry.created, time_entry.updated, time_entry.deleted, timesheet.submitted, timesheet.approved and timesheet.rejected.

Actions

What a workflow can do in Workspace369

Clients

Search, read, create and update: GET or POST /v1/clients, GET or PATCH /v1/clients/{id}.

Projects and tasks

POST /v1/projects and POST /v1/tasks create them; PATCH updates them.

Proposals, invoices and contracts

Create drafts with POST /v1/proposals, /v1/invoices or /v1/contracts. A send call waits for a person to approve it in the app unless the token's owner turned on "send without asking".

Calendar and requests

POST /v1/calendar/events books an event; PATCH /v1/requests/{id} updates a request's status.

Any other tool

POST /v1/tools/{name} runs any tool in the OpenAPI spec by name, such as payments_record or time_entries_create.

How to connect

The built-in Webhook and HTTP Request nodes, as this page describes.

Setup

Setting up n8n

  1. 01

    Add a Webhook node in n8n

    Start a workflow with the Webhook node, set the method to POST and copy the production URL. Turn on the Raw Body option if you will check signatures.

  2. 02

    Add the webhook in Workspace369

    In Settings → Webhooks choose New webhook, paste the n8n production URL as the endpoint, select the events and save. Copy the signing secret; it is shown once. Publish the workflow so the production URL is live.

  3. 03

    Create a personal access token

    In Settings → AI Connections, create a token with only the scopes the workflow needs, and save it as a header credential in n8n. An admin must have turned on AI connections for the workspace.

  4. 04

    Call the API from an HTTP Request node

    Add an HTTP Request node. Set the method and a URL such as https://mcp.workspace369.com/v1/tasks, send Authorization: Bearer followed by your token and a JSON body with the fields.

Operational fit

The connection is only useful when the team can see the context.

Workspace369 keeps the integration close to the client record, so owners, operators, finance, support, and delivery are not rebuilding the same story in separate tools.

Connect the system

Bring the external workflow beside Workspace369 records without changing the way your team names clients, jobs, invoices, and projects.

Keep context visible

Show the relevant status, event, payment, message, or record where the team already works.

Act from the workspace

Use the connected context to follow up, bill, schedule, automate, report, and keep the client moving.

In practice

What teams use n8n for

Running your own automations on your own server

Self-hosted n8n runs the workflow on a server you control, while Workspace369 sends events to it and takes API calls from it.

Creating Workspace369 records from other systems

A form, database or booking tool in n8n can create a client, project, task or calendar event in Workspace369 with one HTTP Request node.

Checking every event before acting

A Code node can verify each event's HMAC-SHA256 signature, so the workflow only runs for requests Workspace369 really sent.

FAQ

Questions about n8n

How does the Workspace369 n8n integration work?
It uses n8n's built-in Webhook and HTTP Request nodes, on n8n Cloud or self-hosted. Workspace369 webhooks send 27 events about clients, invoices, proposals, contracts, bookings, leads and time to a Webhook node, and HTTP Request nodes call the Workspace369 Builder API over HTTPS with a personal access token. There are no events for projects or tasks; a workflow reads those through the API. Self-hosted n8n works if its Webhook URL is a public https:// address on the standard port.#
What is the difference between triggers and actions here?
Triggers come from Workspace369: one of the 27 webhook events starts the workflow. Actions go the other way: an HTTP Request node creates, updates or reads clients, projects, tasks, invoices, proposals, contracts and calendar events through the API. Sending a proposal, contract or invoice returns 202 and waits for a person to approve it in the app, unless the token's owner turned on "send without asking".#
Which Workspace369 plan do I need?
Webhook triggers work on every plan, Cadet included. The Builder API is included on every plan too, trials included. A workflow can also call the same tools through MCP tools/call once an admin turns on AI connections.#
Do n8n workflows use AI usage?
Each action Zapier, Make or n8n runs through the API or MCP uses a little of your workspace's AI usage; reads use less than writes and sends. Failed calls and webhook triggers use none.#
How do I check the webhook signature in n8n?
Turn on the Webhook node's Raw Body option and add a Code node. It computes the hex HMAC-SHA256 of the raw body followed by the X-Webhook-Timestamp header, keyed with your whole whsec_ signing secret, and compares it with X-Webhook-Signature. The Webhook node doesn't check it for you.#
How do I connect Workspace369 to n8n?
The built-in Webhook and HTTP Request nodes connect the two as this page describes.#

See the current Workspace369 in the real app.

Map your clients, requests, communication, projects, billing, payments, AI, automations, accounting, and reporting into one calm workspace.

Start free trial Talk to sales

14-day free trial. Card required. After the trial: $29/month for Cadet. Renews automatically every month until you cancel. Cancel anytime in Settings → Billing.

20+connected modules
24/7client access
Oneoperating view