Resources · Make integration

Sage Sales Management Make integrationAutomate Sage Sales Management with Make.

Can Make keep your Sage Sales Management CRM in step with the rest of your stack? The Sage Sales Management Make integration gives you 43 modules: 12 triggers, 21 actions and 10 searches. This guide walks through the connection, a first scenario and every module in plain words.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Sage Sales Management Make integration do?

The Sage Sales Management Make integration connects your CRM to other apps without writing code. In Make you build a scenario, which is the automation itself: a chain of modules, each one a single brick that watches, creates, finds or updates something. Here those bricks cover accounts, contacts, opportunities, activities, calendar items and sales orders.

No deal left without a next step. Watch Created Opportunities spots each new deal and Create an Event/Task puts a follow-up on the owner's agenda, so a fresh opportunity never sits untouched.

A clean contact base when leads come from elsewhere. A form, a webinar tool or a spreadsheet feeds Create or Update a Contact, which fills in the existing record instead of piling up duplicates. Find an Account can attach the person to the right company first.

Order lines your finance team can reuse. Watch Created Sales Orders followed by List Sales Order Lines hands every line of a new order to your invoicing or reporting tool.

What the integration does not do: none of the 12 triggers is instant, so Make checks Sage Sales Management on the scenario's schedule rather than hearing from it the moment something changes. Anything the listed modules miss goes through Make an API Call. The Make documentation for this app also warns that its text is AI-generated, so check important details with Sage Sales Management itself.

New to the editor? The Make training covers the basics, Make troubleshooting helps when a run fails, and n8n vs Make lays out how the two platforms differ.

Connect

How do you connect Sage Sales Management to Make?

  1. 01

    Copy your two keys from Sage

    In Sage Sales Management, open Settings, then Integrations, then API key management. Copy the API key and the private key shown on that screen. Make needs both: a Public API Key and a Private API Key.

  2. 02

    Open the connection window in Make

    Add any Sage Sales Management module to a scenario and click Create a connection. Typing something in Connection name is optional, but a clear label helps once several accounts are linked.

  3. 03

    Paste the keys and save

    Paste both keys, or follow the on-screen instructions, and confirm. That connection (your Sage account linked to Make once) is then reused by every Sage Sales Management module you add later.

First scenario

Your first scenario: a follow-up task for every new opportunity

GoalWhen a new opportunity appears in Sage Sales Management, Make creates a follow-up event or task for it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module.

  2. 02

    Add Watch Created Opportunities

    Search for Sage Sales Management, pick Watch Created Opportunities and click Create a connection to paste your two keys. The module then watches for deals added to the CRM.

  3. 03

    Add Create an Event/Task

    Click the + on the right of the trigger, pick Create an Event/Task and map data from the opportunity into the task fields Make shows you.

  4. 04

    Test with Run once

    Add a test opportunity in Sage, then click Run once. Open the bubble above each module to read the bundle it received, one opportunity in, one task out.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default; keep it or pick another interval your plan allows, then switch the scenario on.

Triggers

Which Sage Sales Management triggers can start a scenario?

12 modules start a scenario when something happens in Sage Sales Management. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Sage Sales Management as soon as it happens.

Sage Sales Management1Watch Created Accounts

Watch Created Accounts

triggerIn the docs only

This trigger starts your scenario whenever a company record is added to Sage Sales Management. Each new account arrives as one bundle, which is the single item passed on to the next module.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a new account shows up at the next check rather than the instant it is saved.
When to use it
a sales rep signs up a new client company and your billing or project tool needs the same company without anyone retyping it.
Watch out
every account found costs operations in each module after it, so filter out test records early.
Sage Sales Management2Watch Created Activities

Watch Created Activities

triggerIn the docs only

Logged calls, meetings and other activities become a starting point here: the scenario runs on each activity that has just been recorded in the CRM.

How it fires
scheduled. Make looks at the app on the scenario's schedule and picks up every activity created since its previous look.
When to use it
you want a manager alerted in a chat tool, or a line added to a shared sheet, each time a rep reports a visit.
Watch out
busy teams log many activities, and each one is a bundle that consumes operations in every following module, so keep the downstream chain short.
Sage Sales Management3Watch Created Calendar Items

Watch Created Calendar Items

triggerIn the docs only

Think of it as a lookout on the Sage calendar. A new meeting or appointment added there becomes a bundle your scenario can copy, announce or enrich elsewhere.

How it fires
scheduled. Make checks the app on the scenario's schedule, so fresh calendar items arrive in batches, not one by one as they are booked.
When to use it
a rep books a client meeting in Sage and you want a reminder sent through another app or the meeting mirrored in a team calendar.
Watch out
a meeting booked very close to its start time may only reach Make after the next check, so pick an interval that suits the plan you have.
Sage Sales Management4Watch Created Contacts

Watch Created Contacts

triggerIn the docs only

Every person newly saved in Sage Sales Management can open a scenario with this module, whether a rep typed the contact in or another tool created it.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns the contacts created since the last run.
When to use it
new contacts should land in your email marketing tool or receive a welcome sequence without a manual export.
Watch out
if another scenario of yours already writes contacts into Sage, those records show up here too, so check you are not sending them straight back where they came from.
Sage Sales Management5Watch Created Opportunities

Watch Created Opportunities

triggerIn the docs only

New deals are what this trigger catches. Once a rep opens an opportunity in the CRM, your scenario picks it up at the next check and can act on the fresh deal.

How it fires
scheduled. Make checks the app on the scenario's schedule, so the gap between a deal being saved and the scenario starting depends on that interval.
When to use it
every new deal should get a follow-up task, a message to the sales lead or a row in a pipeline report.
Watch out
it reacts to creation only. A deal that changes stage later needs Watch Updated Opportunities instead.
Sage Sales Management6Watch Created Sales Orders

Watch Created Sales Orders

triggerIn the docs only

Signed orders are often where sales hands over to finance or logistics, and this trigger marks that moment by passing each new sales order to your scenario.

How it fires
scheduled. Make checks the app on the scenario's schedule and brings in the orders recorded since the previous check.
When to use it
your invoicing, ERP or warehouse tool needs every order the sales team enters, without anyone forwarding it.
Watch out
when products and quantities matter downstream, add List Sales Order Lines after it to fetch every line of the order.
Sage Sales Management7Watch Updated Accounts

Watch Updated Accounts

triggerIn the docs only

Company records change over time as reps correct them. This module notices accounts that were edited and hands each changed one to your scenario.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns the accounts modified since its last pass.
When to use it
another system keeps its own copy of your clients and must stay aligned with what reps correct in the CRM.
Watch out
if the same scenario later runs Update an Account on that record, the edit may be picked up again at the next check, which can loop.
Sage Sales Management8Watch Updated Activities

Watch Updated Activities

triggerIn the docs only

Here the starting signal is an edit to an activity that already exists, for example a call whose outcome was filled in after the fact.

How it fires
scheduled. Make checks the app on the scenario's schedule and collects the activities changed since the previous run.
When to use it
a report or dashboard should reflect the final notes of a visit, not only the first draft a rep saved.
Watch out
every edited activity runs the modules after it, so filter right after the trigger on the activities your report really needs.
Sage Sales Management9Watch Updated Calendar Items

Watch Updated Calendar Items

triggerIn the docs only

Meetings move, and this trigger is built for that. When an existing calendar item is rescheduled or edited in Sage, the scenario receives the new version.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a moved meeting is picked up at the next check.
When to use it
a meeting copied to another calendar, or announced to a client, must follow the new time instead of keeping the old one.
Watch out
pair it with Watch Created Calendar Items in a separate scenario if you need both new and changed meetings, since this one ignores fresh bookings.
Sage Sales Management10Watch Updated Contacts

Watch Updated Contacts

triggerIn the docs only

A contact whose details get corrected is exactly what this module surfaces: each edited person in the CRM becomes a bundle for your scenario.

How it fires
scheduled. Make checks the app on the scenario's schedule and passes along the contacts edited since the last run.
When to use it
your newsletter tool or support desk holds the same people and should get the corrected details too.
Watch out
writing back to that contact with Update a Contact in the same flow can trigger it again on the next check, so add a filter to break the circle.
Sage Sales Management11Watch Updated Opportunities

Watch Updated Opportunities

triggerIn the docs only

Any edit to an existing deal counts as an update, and this trigger turns each modified deal into input for your scenario.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns the opportunities changed since its previous visit.
When to use it
the team wants a message when a deal moves forward, or a forecast sheet refreshed whenever a rep edits a deal.
Watch out
every edit counts, even a typo fix, so add a filter after the trigger on the change you care about before spending operations further down.
Sage Sales Management12Watch Updated Sales Orders

Watch Updated Sales Orders

triggerIn the docs only

Orders that already exist but get edited later are handed to your scenario by this module.

How it fires
scheduled. Make checks the app on the scenario's schedule and lists the sales orders modified since it last looked.
When to use it
finance or logistics already received the order and needs the revised version, not a second copy of the original.
Watch out
to see the current products and quantities as well, follow it with List Sales Order Lines rather than assuming the order carries them.
Modules

What can the Sage Sales Management modules do?

Sage Sales Management gives you 31 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Sage Sales Management1

Create a Contact

ActionIn the docs only

Adds a brand-new person to Sage Sales Management from data collected anywhere else in your scenario, such as a web form or a spreadsheet row.

When to use it
you are sure the person does not exist yet, for example right after a search came back empty.
Watch out
run twice on the same person, it creates two records; Create or Update a Contact avoids that.
Sage Sales Management2

Create a Sales Order

ActionIn the docs only

Opens a new order in the CRM, so a sale closed in a shop, a quote tool or a form is recorded where your sales team works.

When to use it
a payment or signed quote in another app should become an order in Sage without retyping.
Watch out
the order body and its products are separate; add Create a Sales Order Line for each item.
Sage Sales Management3

Create a Sales Order Line

ActionIn the docs only

Attaches one product line to an existing order. Paired with Create a Sales Order, it rebuilds a full order piece by piece.

When to use it
the source app sends a basket with several products and each one must appear on the Sage order.
Watch out
one line means one operation, so a large basket runs this module once per item and counts each run on your plan.
Sage Sales Management4

Create an Account

ActionIn the docs only

Registers a new company in Sage Sales Management, giving contacts, deals and orders a place to hang from.

When to use it
a new client signs up in your billing or onboarding tool and the sales team should see the company right away.
Watch out
nothing here checks for an existing company with the same name; search first with Find an Account or use Create or Update an Account.
Sage Sales Management5

Create an Activity

ActionIn the docs only

Logs an interaction on the CRM timeline, so calls, emails or visits handled in another tool still leave a trace next to the client.

When to use it
your phone system or email tool records a conversation and reps should find it in Sage without copying notes by hand.
Watch out
an activity is a record of what happened; to plan something ahead, Create an Event/Task fits better.
Sage Sales Management6

Create an Entity

ActionIn the docs only

Writes a record of a type you choose, which helps when the object you need has no dedicated create module on this list.

When to use it
the specific modules for accounts, contacts or deals do not cover the object your team works with.
Watch out
being generic, it covers several record types, so check which one you target and test with Run once before letting it write real data.
Sage Sales Management7

Create an Event/Task

ActionIn the docs only

Puts something to do on a rep's plate: a meeting to hold or a task to complete, scheduled inside Sage Sales Management.

When to use it
a new deal, a form reply or a late payment should end with a clear next step assigned to someone.
Watch out
map the owner carefully; if you pull the user from Get a User or List Users, the task lands with the right person.
Sage Sales Management8

Create an Opportunity

ActionIn the docs only

Turns a promising signal from another app into a deal in the pipeline, ready for a rep to qualify and move forward.

When to use it
a demo request, a quote request or a hot lead score elsewhere should open a deal without waiting for someone to notice.
Watch out
attach it to the right company by finding the account first with Find an Account, otherwise the deal floats on its own.
Sage Sales Management9

Create or Update a Contact

ActionIn the docs only

Keeps one record per person: if the contact exists it gets refreshed, if not it gets created, all in a single module.

When to use it
leads arrive from several sources and the same person may show up more than once, like a webinar attendee who later fills a form.
Watch out
test with Run once on an existing contact to see what gets replaced, and avoid mapping empty values over fields reps filled in.
Sage Sales Management10

Create or Update an Account

ActionIn the docs only

The safe way to sync companies: an existing account is updated, a missing one is created, and you do not need a search module in front.

When to use it
another system is your reference for client companies and Sage should mirror it without duplicates.
Watch out
an update can replace what reps typed, so decide which source should win before letting both tools write to the same company.
Sage Sales Management11

Find a Contact

SearchIn the docs only

Looks up people already in the CRM and returns what it finds, so the scenario can reuse an existing record instead of guessing.

When to use it
before logging an activity or creating a deal, you need the contact that matches an email or a name from another app.
Watch out
a search can return zero, one or several bundles; plan what happens in each case, especially when nothing matches.
Sage Sales Management12

Find an Account

SearchIn the docs only

Searches your companies so a scenario can link new data to the right client rather than creating a lookalike.

When to use it
an order, a deal or a contact from another tool must be attached to a company that should already exist in Sage.
Watch out
two companies with similar names can both come back; add a filter or a tighter search so the wrong account is never picked.
Sage Sales Management13

Find an Entity

SearchIn the docs only

A general-purpose search across the record types of Sage Sales Management, handy for objects with no dedicated find module.

When to use it
you need records of a type that Find a Contact, Find an Account or Find an Opportunity do not reach.
Watch out
like any search, it may return several bundles, and each one runs the modules after it, which adds operations.
Sage Sales Management14

Find an Opportunity

SearchIn the docs only

Retrieves deals already in the pipeline so your scenario can update or comment on them instead of opening new ones.

When to use it
a signed quote or a payment arrives elsewhere and you want the deal it belongs to before calling Update an Opportunity.
Watch out
an empty result is common with new clients; route that case toward Create an Opportunity rather than letting the scenario stop.
Sage Sales Management15

Get a Sales Order Line

ActionIn the docs only

Fetches one precise line of an order when you already know which one you want, giving the scenario its full content.

When to use it
an earlier module handed you a line reference and you need its details before updating it or passing them on.
Watch out
it returns a single line; to walk through every line of an order, List Sales Order Lines is the right pick.
Sage Sales Management16

Get a User

ActionIn the docs only

Reads the profile of one member of your Sage Sales Management team, useful to know who owns a record before acting on it.

When to use it
a trigger gives you the owner of a deal and you want that person's details to notify them or assign a task.
Watch out
it works on one known user; to browse the whole team and choose, use List Users instead.
Sage Sales Management17

List Branches

SearchIn the docs only

Returns the branches set up in your Sage account, handy when records must be tied to the right office or business unit.

When to use it
a scenario serves several branches and you need the correct one before creating an account or an order.
Watch out
each branch comes back as its own bundle, so everything placed after this module runs once per branch.
Sage Sales Management18

List Countries

SearchIn the docs only

Gives you the country values Sage Sales Management knows, so an address from another app can be matched to one the CRM accepts.

When to use it
a form sends country names in its own spelling and you want the Sage version before writing an account or contact.
Watch out
one bundle per country; add a filter right after it, or the rest of the scenario repeats for every country on the list.
Sage Sales Management19

List Currencies

SearchIn the docs only

Returns the currencies configured in your CRM, a helper for any scenario that writes amounts on deals or orders.

When to use it
your shop or quote tool sells in more than one currency and the order in Sage must carry the matching value.
Watch out
it lists, it does not convert; any exchange rate calculation has to come from another source.
Sage Sales Management20

List Sales Order Lines

SearchIn the docs only

Brings back all the lines of an order, one bundle per line, so products and quantities can travel to another tool.

When to use it
right after Watch Created Sales Orders, when your invoicing or warehouse app needs the detail and not only the order header.
Watch out
long orders multiply bundles, and each following module counts one operation per line on your plan.
Sage Sales Management21

List Timezones

SearchIn the docs only

Returns the time zones Sage Sales Management accepts, which saves guesswork when a scenario creates meetings for people in different regions.

When to use it
you plan events with Create an Event/Task for reps or clients spread across countries and want the correct zone.
Watch out
every entry is a bundle; filter it straight away to keep only the zone you need.
Sage Sales Management22

List Users

SearchIn the docs only

Pulls the members of your Sage team, so the scenario can pick who should own a new record or receive a task.

When to use it
leads must be spread among reps, or you need to match a user from another tool to their Sage profile.
Watch out
you get one bundle per user; without a filter, the next modules fire for the whole team.
Sage Sales Management23

Make an API Call

ActionIn the docs only

Opens the rest of the Sage Sales Management API from inside your scenario, with the connection you already set up.

When to use it
the object or action you need is not among the 43 listed modules, so you call the endpoint yourself.
Watch out
you write the request by hand here, so read the Sage API documentation for the endpoint and test with Run once first.
Sage Sales Management24

Update a Contact

ActionIn the docs only

Changes the details of a person who is already in the CRM, keeping the same record and its history.

When to use it
a customer edits their profile in your support desk or shop, and reps should see the corrected details in Sage.
Watch out
you need the contact's reference first, usually from Find a Contact, since the update aims at one precise record.
Sage Sales Management25

Update a Sales Order

ActionIn the docs only

Edits an order that already exists, so a change made in finance or logistics also shows on the sales side.

When to use it
an order gets shipped, cancelled or amended in another system and the Sage version should say so.
Watch out
this touches the order itself, not its products; lines are changed with Update a Sales Order Line.
Sage Sales Management26

Update a Sales Order Line

ActionIn the docs only

Corrects a single product line on an order, so one item can change while the others stay as they are.

When to use it
stock runs short or a client revises one item, and only that line should move while the rest of the order stays intact.
Watch out
target the right line by pulling it first with Get a Sales Order Line or List Sales Order Lines.
Sage Sales Management27

Update an Account

ActionIn the docs only

Refreshes company data in the CRM without creating a new record, so the account keeps its contacts and deals.

When to use it
your billing tool or registry holds newer company details and Sage should catch up.
Watch out
combined with Watch Updated Accounts, this edit can fire the trigger again; filter on the source to avoid a loop.
Sage Sales Management28

Update an Activity

ActionIn the docs only

Completes or corrects an activity already logged, for instance adding the result of a call once it is known.

When to use it
your call or meeting tool produces a summary after the fact and it belongs on the activity the rep created earlier.
Watch out
the scenario needs the activity reference, so keep it from the step that created or found that activity.
Sage Sales Management29

Update an Entity

ActionIn the docs only

Edits a record of any type you choose, the counterpart to Create an Entity for objects without a specific update module.

When to use it
the record you need to change is not an account, contact, deal, activity or order.
Watch out
pick the entity type and record with care, because a generic module will happily edit the wrong object if you point it there.
Sage Sales Management30

Update an Event/Task

ActionIn the docs only

Moves or edits a planned event or task, keeping the rep's agenda in Sage aligned with what really happens.

When to use it
a client reschedules through a booking tool, or a task is done elsewhere and should be marked in the CRM.
Watch out
without the event reference the update has nothing to aim at, so carry it from the module that created the item.
Sage Sales Management31

Update an Opportunity

ActionIn the docs only

Pushes new information onto a deal, straight from another tool, so the pipeline reflects what happened elsewhere.

When to use it
a quote gets signed or a payment clears elsewhere and the pipeline in Sage should move without a rep touching it.
Watch out
find the deal first with Find an Opportunity, and watch for loops if Watch Updated Opportunities runs in another scenario.
Need help

Need help automating Sage Sales Management with Make?

A person reads every message.

FAQ

Common questions about Sage Sales Management and Make

01Is the Sage Sales Management Make integration free?
Yes, on the Make side. Sage Sales Management is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the minimum interval to 1 minute and count usage in credits, also called operations. You still need your own Sage Sales Management account; its subscription is described on the Sage Sales Management pricing page.
02What is needed to connect Sage Sales Management to Make?
A Sage Sales Management account and two keys: a Public API Key and a Private API Key. You find both in Sage under Settings, then Integrations, then API key management, where the API key and the private key are displayed on screen. In Make, add any module of the app, click Create a connection, give it a name if you like, and paste the two keys. The connection is then shared by every Sage Sales Management module in your scenarios, so you only do this once per account.
03Do Sage Sales Management triggers in Make react in real time?
No. All 12 triggers are scheduled, and none is instant. Make checks Sage Sales Management on the scenario's schedule, which is every 15 minutes by default for a new scenario. On the Free plan 15 minutes is also the shortest interval allowed, while paid plans go down to 1 minute. So a new contact or an edited deal reaches your scenario at the next check, not the second it is saved. For most CRM syncs that delay is fine, but plan for it if a follow-up is urgent.
04What if a Sage Sales Management module is missing in Make?
Use Make an API Call. It calls any endpoint of the Sage Sales Management API with the connection you already set up, so you can reach objects or actions that the listed modules do not cover. Create an Entity, Find an Entity and Update an Entity are also worth a look first, since they work across record types. Keep in mind that the Make documentation for this app says its text is AI-generated and may contain mistakes, so confirm important details with Sage Sales Management directly.
05Should Sage Sales Management be automated with Make or n8n?
It depends on the tool your team already uses. In Make, Sage Sales Management comes with 43 ready modules, a visual editor and a Free plan to test with, which suits people who want to start without code. The same app often has a node in n8n as well, so check that the node you need exists there before choosing. Neither answer is right for everyone: compare the modules each side offers for your exact task, then pick the platform your team will actually maintain.