Resources · n8n integration

Salesmate n8n integrationAutomate Salesmate with n8n.

Your CRM should not wait for someone to retype what already happened elsewhere. The Salesmate n8n integration puts 15 operations across 3 resources into your workflows: activities, companies and deals, created, read, updated or deleted on their own. Salesmate has no trigger node, so the workflow starts somewhere else.

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Salesmate n8n integration give you?

The Salesmate node ships with n8n and exposes 15 operations spread over 3 resources: activities, companies and deals. Each operation is one call against your own Salesmate account, authenticated once with a Session Token and your Salesmate URL. You shape the record on one side of the workflow, the node writes it, reads it back or removes it on the other.

First scenario, the inbound lead that turns into a real opportunity. A form submission arrives in a workflow, company.create registers the account under its Name with an owner attached, then deal.create opens the opportunity in the Sales pipeline at the New (Untouched) stage. The rep opens a qualified record instead of an inbox to triage, and the account already carries the owner who will follow it up.

Second scenario, the follow-up nobody forgets. Once a call is logged, activity.create writes the next task with its Title, its Type and a Due Date. A scheduled run of activity.getAll then copies that workload into a Google Sheets tab, or posts it as a morning digest in Slack.

Third scenario, a CRM that keeps up with what happens outside it. A payment in Stripe or an order in WooCommerce feeds company.update to refresh the billing address, and deal.update to move the Status to Close. The same figure never gets typed twice.

The node covers the 15 operations documented below. For any other Salesmate endpoint, the HTTP Request node calls the API directly and reuses the very same credential through predefined authentication, so everything still lives in one workflow.

One habit to pick up early: the three list operations stop at Limit unless Return All is switched on, and with it on, n8n chains the API pages for you. Useful when a Salesmate export has to be complete rather than fast. If you are still comparing CRMs to automate, the Pipedrive and HubSpot nodes are built on the same logic.

Connect

How do you connect Salesmate to n8n?

  1. 01

    Generate the access key in Salesmate

    In Salesmate, go to My Account > Access Key and generate an access key. That value is what n8n asks for under the name Session Token. While you are there, note your Salesmate domain name, the base URL you sign in with every morning, written in the form n8n.salesmate.io. Both are needed in the next step.

  2. 02

    Store the credential once in n8n

    Open the Credentials menu in n8n and create a Salesmate credential. Salesmate authenticates with an API token, so there are exactly two fields to fill: Session Token with the access key, URL with your domain. A credential is saved once and reused by every workflow on the instance, which is why the key never gets pasted into a node.

  3. 03

    Select it in the node and test

    Drop a Salesmate node on the canvas and pick the credential from the dropdown, where n8n lists the ones you already saved. Choose a resource, Activity, Company or Deal, then an operation. Run the node once on Get many companies: it needs no required field, so a clean answer tells you the authentication works before you wire anything else.

Actions

What can the Salesmate node do?

The Salesmate node exposes 15 operations across 3 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetGet ManyUpdateDelete
Activity✓✓✓✓✓
Company✓✓✓✓✓
Deal✓✓✓✓✓

Activity

5 operations
01

Create an activity

activity.create

What you see in n8n

Notes & use cases

Writes a new activity in Salesmate, the call, meeting or task somebody has to run.

Key parameters

  • Title: the line that shows up in the activity list, for instance the subject of the call to place.
  • Owner Name or ID: the Salesmate user in charge, chosen from the dropdown or passed as an ID with an expression such as {{ $json.field }}.
  • Type: the activity type, call or meeting for example.
  • Due Date: in Additional Fields, the expiry date of the activity.
  • Is Calendar Invite: also there, decides whether a calendar invite goes out.
Use cases
a demo request lands and the follow-up call is booked on the account owner, invite included.
02

Delete an activity

activity.delete

What you see in n8n

Notes & use cases

Removes one or several activities from Salesmate, identified by their id, and nothing else in the record survives the call.

Key parameters

  • Activity ID: the identifier of the activity to remove. More than one goes into the same field, separated by commas, which lets a single node clear a batch.
Use cases
a prospect replies that the project is on hold, and the tasks a sequence had queued for the next two weeks get wiped in one node instead of being closed one by one.
03

Get an activity

activity.get

What you see in n8n

Notes & use cases

Fetches a single activity so the workflow can read it before deciding what happens next.

Key parameters

  • Activity ID: the identifier of the activity to read, usually carried over from an earlier node with an expression like {{ $json.field }}.
  • RAW Data: switched on, the data that comes back includes the fields details rather than the shorter version.
Use cases
before a reminder goes out, the workflow reloads the activity and checks what it actually says, so the message quotes the real subject line.
04

Get many activities

activity.getAll

What you see in n8n

Notes & use cases

Returns a list of activities, which is how you get a view of the team workload without opening Salesmate.

Key parameters

  • Return All: on, n8n chains the API pages and brings back every activity; off, the run stops at Limit.
  • Limit: the maximum number of activities the node returns.
  • Fields: in Options, a comma separated list of the fields to return, handy when only a couple of columns end up in the report.
  • Sort By and Sort Order: the field to sort on, ascending with asc or descending with desc.
Use cases
every Monday morning, the week's activities are pulled and dropped into a shared sheet.
05

Update an activity

activity.update

What you see in n8n

Notes & use cases

Changes an activity that already exists. Only the fields you fill under Update Fields are touched, the rest stays as it was.

Key parameters

  • Activity ID: which activity gets the change.
  • Is Completed: in Update Fields, whether the activity counts as completed.
  • Duration: the time duration of the activity, useful once the call is over and you know how long it really took.
  • Tags: the tags associated with the activity.
Use cases
a call ends, the telephony tool closes the loop, and the matching activity is marked done with its real duration.

Company

5 operations
06

Create a company

company.create

What you see in n8n

Notes & use cases

Registers a new account in Salesmate, the company side of the CRM that deals and activities later hang from.

Key parameters

  • Name: the company name, the only piece of identity the operation refuses to run without.
  • Owner Name or ID: the Salesmate user who owns the account, from the dropdown or as an ID through an expression.
  • Website and Phone: in Additional Fields, the two details a rep looks for first.
  • Billing City and Billing State: also in Additional Fields, when invoicing data travels with the account.
Use cases
a signup form fills the account the moment a company email address is detected.
07

Delete a company

company.delete

What you see in n8n

Notes & use cases

Erases an account from Salesmate. Worth aiming carefully, since a company sits above everything attached to it.

Key parameters

  • Company ID: the identifier of the account to erase. Several of them go in the same field separated by commas, so one node handles a whole cleanup list.
Use cases
a deduplication routine spots two records for the same business, keeps the one with the richer history and sends the other identifier here.
08

Get a company

company.get

What you see in n8n

Notes & use cases

Reads one account and drops its content into the workflow, which is the step that turns an identifier into something usable.

Key parameters

  • Company ID: the identifier of the account to load.
  • RAW Data: on, the response carries the fields details instead of the shorter payload.
Use cases
a support ticket arrives with an account identifier, the workflow loads the company and routes the ticket to the owner named on the record.
09

Get many companies

company.getAll

What you see in n8n

Notes & use cases

Brings back accounts as a list, the operation you reach for when Salesmate has to feed another system rather than answer one question.

Key parameters

  • Return All: on for a complete export, n8n walks the API pages itself; off, the node stops at Limit.
  • Limit: how many accounts come back at most.
  • Fields: in Options, the comma separated list of fields to return.
  • Sort By: in Options, the field the list is sorted on.
Use cases
a nightly run rebuilds the account directory the finance team reads, complete rather than truncated.
10

Update a company

company.update

What you see in n8n

Notes & use cases

Applies changes to an existing account, field by field, through the Update Fields collection.

Key parameters

  • Company ID: the account being edited.
  • Billing Address Line 1 and Billing Zip Code: in Update Fields, the address details that change when a client moves.
  • Owner Name or ID: in Update Fields too, to hand the account over to another rep.
  • Tags: the tags carried by the account.
Use cases
a customer edits the billing address in your product, and the CRM record follows within the minute.

Deal

5 operations
11

Create a deal

deal.create

What you see in n8n

Notes & use cases

Opens an opportunity in Salesmate. This is the operation with the longest list of required fields, because a deal has to land somewhere precise in the pipeline.

Key parameters

  • Title, Owner Name or ID and Primary Contact Name or ID: what the deal is called, who runs it, who it is with.
  • Pipeline, Status and Stage: Sales for the pipeline, Open to start, New (Untouched) for a deal nobody has worked yet.
  • Currency and Deal Value: the currency is required, the amount sits in Additional Fields.
Use cases
a signed quote creates the deal already priced and assigned.
12

Delete a deal

deal.delete

What you see in n8n

Notes & use cases

Takes deals out of Salesmate for good, which matters more here than elsewhere: a deleted opportunity no longer weighs on the pipeline.

Key parameters

  • Deal ID: the identifier of the opportunity to remove, several at once in the same field separated by commas.
Use cases
a test campaign generated a batch of dummy opportunities, and the list of their identifiers goes through one node so the forecast stops counting fiction.
13

Get a deal

deal.get

What you see in n8n

Notes & use cases

Loads a single opportunity, so the workflow can act on what the deal says right now instead of on what it said an hour ago.

Key parameters

  • Deal ID: the identifier of the opportunity to read.
  • RAW Data: on, the data includes the fields details.
Use cases
before a contract is generated, the workflow reloads the deal and builds the document from the values stored in Salesmate, not from the ones the form collected earlier.
14

Get many deals

deal.getAll

What you see in n8n

Notes & use cases

Lists opportunities, which is the shortest route to a pipeline snapshot outside the CRM.

Key parameters

  • Return All: on, every deal comes back page after page; off, the node stops at Limit.
  • Limit: the ceiling on the number of deals returned.
  • Sort Order: in Options, asc or desc, enough to put the top of the list where you want it.
  • Fields: in Options, the comma separated list of fields to return.
Use cases
a weekly recap of open opportunities lands in the sales channel before the pipeline review.
15

Update a deal

deal.update

What you see in n8n

Notes & use cases

Moves a deal along, or corrects it. Everything happens in Update Fields, and untouched fields keep their value.

Key parameters

  • Deal ID: the opportunity being edited.
  • Stage: Contacted, Qualified, In Negotiation or Proposal Presented, the way an automation advances a deal.
  • Status: Open, Close or Lost.
  • Estimated Close Date and Priority: the expected date and High, Medium or Low.
Use cases
a proposal is opened by the prospect and the deal jumps to Proposal Presented without the rep touching it.
Need help

Need help automating Salesmate with n8n?

A person reads every message.

FAQ

Salesmate and n8n, the questions that come up

01Is the Salesmate n8n integration free?
Yes, on the n8n side. The Salesmate node ships with n8n: nothing to install, no add-on to buy, and it behaves the same way on n8n Cloud, the hosted offer run by n8n, as on a self-hosted instance under the Community Edition and its Sustainable Use licence. A workflow built in one place runs in the other without changes. What Salesmate itself costs is a separate question and this page does not answer it, since the only thing needed on that side is an account able to generate an access key.
02What credentials do you need to connect Salesmate?
Salesmate authenticates with an API token, and the credential holds two values. The Session Token is an access key, generated in Salesmate from the Access Key page of your own account. The URL is your Salesmate domain name, the base URL of your account, written in the form of a domain rather than a full endpoint. You create that credential once in the Credentials menu of n8n, and every workflow on the instance can then select it from the node dropdown. Nothing else is asked, and the key itself never has to be pasted into a node.
03What are the limits of the Salesmate node?
The node exposes 15 operations over 3 resources, activities, companies and deals, each with create, read, list, update and delete. On the three list operations, the result stops at Limit unless Return All is enabled, in which case n8n chains the API pages to bring everything back. For any Salesmate endpoint outside that catalogue, the HTTP Request node calls the API directly and reuses the same credential through predefined authentication, so you do not need a second connection or a second workflow to reach it.
04Can a workflow react to changes in Salesmate in real time?
Not from Salesmate itself. There is no Salesmate trigger node in n8n, so a workflow that touches Salesmate starts somewhere else. Three usual routes: a Schedule Trigger that runs at a fixed interval and calls Get many deals, Get many companies or Get many activities to work on what it finds; an n8n Webhook, a URL that another service calls when something happens on its side; or the trigger of another tool already in your setup, a form, a payment tool, a helpdesk. Salesmate then receives the write once the workflow is already running.
05n8n or Make to automate Salesmate?
It depends on four things. Hosting: n8n runs self-hosted with Docker or npm, or on n8n Cloud, while Make is hosted only. Data control: on a self-hosted instance, the CRM records passing through a workflow stay on infrastructure you own. Cost model: Make bills per operation, which is worth simulating against a workflow that lists every company every night. Visual logic: both draw the flow on a canvas, and the fastest way to decide is to rebuild one real Salesmate scenario in each and compare the number of steps.