Yearly plans: first year for the price of 6 months

Connect Workspace369 to Make (Integromat)

Connect Workspace369 to Make (formerly Integromat) today with Make's Webhooks and HTTP apps. A paid invoice, a signed contract or a new lead starts a scenario, and an HTTP module creates or reads clients, invoices, tasks and projects through the Workspace369 API.

Talk to sales Explore features
Scenario run
contract.completedPOST hook.<region>.make.com/… → 200
HTTPGET mcp.workspace369.com/v1/contracts/{id} → 200
HTTPPOST mcp.workspace369.com/v1/projects → 200

Workspace369 events in, API calls out

Connected records

Keep client context attached

Make 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.

Works inside

Invoices Proposals Contracts Time tracking CRM

How it works

How Make works with Workspace369

  1. 01

    Workspace369 sends the trigger

    In Settings → Webhooks you point events at a Make Custom webhook URL. Each event arrives as signed JSON with the record's id.

  2. 02

    Make runs your scenario

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

  3. 03

    HTTP modules call the API

    The HTTP app's Make a request module calls the Workspace369 API over plain HTTPS with your personal access token.

Triggers

The 21 events that can start a scenario

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.

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 scenario 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.

Native app

In development. Until then, Make's Webhooks and HTTP apps are the way to connect.

Setup

Setting up Make

  1. 01

    Add a Custom webhook in Make

    Start a scenario with the Webhooks app's Custom webhook trigger and copy its URL. Turn on Get request headers if you will check signatures.

  2. 02

    Add the webhook in Workspace369

    In Settings → Webhooks choose New webhook, paste the Make URL as the endpoint, select the events and save. Copy the signing secret; it is shown once. Then do something that fires the event, such as creating an invoice, so Make can work out the data structure.

  3. 03

    Create a personal access token

    In Settings → AI Connections, create a token with only the scopes the scenario needs. An admin must have turned on AI connections for the workspace.

  4. 04

    Call the API from an HTTP module

    Add the HTTP app's Make a request module. Set the method and a URL such as https://mcp.workspace369.com/v1/projects, send Authorization: Bearer followed by your token, choose a JSON body and map 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 Make for

Starting work when a client signs

contract.completed or proposal.accepted starts a scenario that sets up folders, channels or onboarding in the other tools you use.

Creating Workspace369 records from other apps

A form, spreadsheet or booking app in Make can create a client, project, task or calendar event in Workspace369 with one HTTP module.

Keeping finance and payroll in step

invoice.paid and timesheet.approved feed your bookkeeping sheet, finance tool or payroll report.

FAQ

Questions about Make

How do I connect Workspace369 to Make (Integromat)?
Use Make's Webhooks and HTTP apps; Make was formerly called Integromat. Workspace369 webhooks send 21 events about invoices, proposals, contracts, leads and time to a Make Custom webhook, and HTTP Make a request modules call the Workspace369 Builder API over HTTPS with a personal access token. There are no events for clients, projects, tasks or bookings; a scenario reads those through the API.
What is the difference between triggers and actions here?
Triggers come from Workspace369: one of the 21 webhook events starts the scenario. Actions go the other way: an HTTP module 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?
Specialist ($149 a month, 10 seats) and higher. Webhook triggers and the Builder API both need Specialist. On Cadet and Voyager, a workflow can still call the same tools through MCP tools/call once an admin turns on AI connections, but it can't receive webhook triggers.
Do Make 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.
Can Make check the webhook signature?
Not on its own: a Custom webhook accepts any request to its URL. Turn on Get request headers and add a step that runs code to compute the hex HMAC-SHA256 of the raw body followed by the X-Webhook-Timestamp header, keyed with your whole whsec_ signing secret, and compare it with X-Webhook-Signature. Or treat the event as a notice and fetch the record from the API before acting on it.
Is there a native Workspace369 app in Make?
Not yet. A native Make app is in development. Until it is ready, Make's Webhooks and HTTP apps connect the two as this page describes.

Keep exploring

Related pages

ZapierThe same events and API calls in Zaps.n8nThe same setup with n8n's Webhook and HTTP Request nodes.WebhooksEvery event, the signature and retries.API workflowsCall Workspace369 from your own code.PricingCompare plans, including Specialist.

More from Workspace369

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: from $29/month. Renews automatically every month until you cancel. Cancel anytime in Settings → Billing.

20+connected modules
24/7client access
Oneoperating view