Resources · Make integration

SharpSpring Make integrationAutomate SharpSpring with Make.

Sync SharpSpring leads and deals with the rest of your stack, without writing code. The SharpSpring Make integration gives you 26 modules: 4 triggers, 17 actions and 5 searches. This guide connects your account and walks you through a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SharpSpring Make integration automate?

The SharpSpring Make integration links your SharpSpring account to Make, so Make can spot new leads, accounts, form submissions and opportunities, then create, update, read or delete those records for you. You build the logic once as a scenario (the automation you assemble in Make) and it keeps running on its own.

Turn a form into a deal. Watch Forms notices when a lead fills out one of your SharpSpring forms, and Create an Opportunity opens the matching deal so sales can follow up without retyping anything.

Keep campaigns tidy from another tool. When a project starts in your planning app, Create a Campaign sets it up in SharpSpring; Update a Campaign and Delete a Campaign handle the rest of its life.

Pull a lead report on demand. Search Leads returns the leads of a date range you pick, and each one travels to a spreadsheet such as the one described on our Airtable Make integration page.

What Make does not do here: none of the four SharpSpring triggers is instant, so Make checks for news on the scenario's schedule rather than the moment it happens. Anything the 26 modules skip can still be reached with Make an API Call.

SharpSpring may also exist as an n8n node; our n8n vs Make comparison helps you choose, and the Make training covers the editor from scratch.

Connect

How do you connect SharpSpring to Make?

  1. 01

    Have your API Key ready

    Make needs an active SharpSpring account and an API Key. Copy the credentials from your SharpSpring account before you open Make, so the connection (your SharpSpring account linked to Make once) takes a single pass.

  2. 02

    Add a SharpSpring module

    Log in to Make, add any SharpSpring module to your scenario and click Create a connection. You can type a label in the Connection name field; it is optional but handy if you manage several SharpSpring accounts.

  3. 03

    Paste the credentials

    Enter the credentials you copied from SharpSpring, or follow the instructions Make shows on screen, then save. Every other SharpSpring module in your scenarios reuses this same connection.

First scenario

Your first scenario: a form submission becomes an opportunity

GoalWhen a lead fills out a form in SharpSpring, Make creates an opportunity for that lead.

  1. 01

    Create the scenario

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

  2. 02

    Add Watch Forms

    Search for SharpSpring, pick Watch Forms and select your connection, or click Create a connection if this is your first SharpSpring module.

  3. 03

    Fill in the trigger

    Complete the module fields. Once the connection exists, Make lists what it can read in your account, so you pick from a menu instead of typing IDs.

  4. 04

    Add Create an Opportunity

    Click the + to the right of Watch Forms, choose Create an Opportunity and map the lead data coming from the form into its fields.

  5. 05

    Test with Run once

    Submit a test form in SharpSpring, then click Run once. Open each module's bubble to read the bundles (one item passed along, here one submission) it received.

  6. 06

    Schedule and switch on

    On the first module, set the schedule (every 15 minutes by default, 15 at the shortest on the Free plan) and turn the scenario on.

Triggers

What starts a SharpSpring scenario?

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

SharpSpring1Watch Accounts

Watch Accounts

Scheduled trigger

In MakeTriggers when a new account is created.

Your scenario starts each time a new account appears in SharpSpring, so the company record can be copied or announced elsewhere without anyone exporting it by hand.

How it fires
scheduled. Make checks SharpSpring on the scenario's schedule and picks up the accounts created since its last look; the clock badge on the module reminds you of that.
When to use it
a sales rep adds a new client company, and finance needs a matching customer file in its own tool.
Watch out
it reacts to new accounts only; a later edit to an existing company will not start your scenario.
SharpSpring2Watch Forms

Watch Forms

Scheduled trigger

In MakeTriggers when a lead fills out a form.

Every SharpSpring form a lead fills out becomes a bundle Make can pass along, which lets you act on a demo request or a quote request without opening the SharpSpring inbox.

How it fires
scheduled. Make asks SharpSpring for new submissions on the scenario's schedule, every 15 minutes by default, and never faster than 15 minutes on the Free plan.
When to use it
a contact form on your pricing page that should open a deal or ping the right salesperson.
Watch out
each submission counts as operations for every module that processes it, so keep the flow short on a busy form.
SharpSpring3Watch Leads

Watch Leads

Scheduled trigger

In MakeTriggers when a new lead is created.

Make picks up every lead newly created in SharpSpring and hands it to the next modules, whether the lead came from a form, an import or a colleague's manual entry.

How it fires
scheduled. Make queries SharpSpring on the scenario's schedule, so a lead created now reaches your scenario at the next run rather than instantly.
When to use it
welcoming each new lead in your chat tool or adding it to a separate nurturing list.
Watch out
if the next step is Create a Lead in SharpSpring itself, the new record would be picked up again on the following run, so send leads out, not back in.
SharpSpring4Watch Opportunities

Watch Opportunities

Scheduled trigger

In MakeTriggers when a new opportunity is created.

This trigger tells Make about each new opportunity created in SharpSpring, so every deal your pipeline gains can set off a follow-up.

How it fires
scheduled. Make checks SharpSpring at the interval set on the scenario, as shown by the clock badge; paid plans can shorten it down to 1 minute.
When to use it
a sales manager wants a message in the team channel, or a line in a forecast sheet, whenever a deal is opened.
Watch out
the module is described as reacting to new opportunities, so do not count on it to follow stage changes on existing deals.
Modules

What can Make do in SharpSpring?

SharpSpring gives you 22 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SharpSpring1

Create a Campaign

Action

In MakeCreates a new campaign.

Sets up a new campaign in SharpSpring from data another app already holds, so the campaign exists as soon as the project is approved.

When to use it
a marketing brief is validated in your project tool and should appear in SharpSpring without a second manual entry.
Watch out
every run of this module creates one more campaign, so make sure the trigger fires only once per approved project.
SharpSpring2

Create a Lead

Action

In MakeCreates a new lead.

Adds a person to SharpSpring as a lead, straight from wherever that person first showed up: a webinar sign-up, an event badge scan list, a chatbot conversation.

When to use it
your event tool collects attendees and you want each one in SharpSpring for follow-up.
Watch out
check first with Search Leads or List Leads if duplicates worry you.
SharpSpring3

Create an Account

Action

In MakeCreates a new account.

Opens a company record in SharpSpring so leads and opportunities have an account to hang from, filled with data mapped from the previous module.

When to use it
a signed contract in your e-signature app means a new client company that sales should find in SharpSpring.
Watch out
if the company may already be in SharpSpring, look it up first with List Accounts so you do not end up with two records.
SharpSpring4

Create an Opportunity

Action

In MakeCreates a new opportunity.

Records a deal in your SharpSpring pipeline from an event that happened somewhere else, so no sales signal is left in an inbox.

When to use it
a form submission caught by Watch Forms, or a quote accepted in your billing tool, should become a deal to follow.
Watch out
map at least the fields your team relies on in its pipeline views, or the deal will be hard to find.
SharpSpring5

Delete a Campaign

Action

In MakeDeletes a campaign from your account.

Removes a campaign from your SharpSpring account, which keeps the campaign list clean when a project is dropped in the tool where it was planned.

When to use it
a project is cancelled in your planning app and its campaign no longer has a reason to exist.
Watch out
a deletion cannot be undone from Make; add a filter so only the intended campaign reaches this module.
SharpSpring6

Delete a Lead

Action

In MakeDeletes a lead from your account.

Erases a lead from SharpSpring, useful when a person asks to be forgotten or when a test record slipped into the database.

When to use it
a removal request logged in your support tool should wipe the matching lead as well.
Watch out
Make cannot bring the lead back; test on a dummy lead with Run once before switching the scenario on.
SharpSpring7

Delete an Account

Action

In MakeDeletes an account from your account.

Removes a company record from SharpSpring once it has no place in your CRM anymore, for example after a merger or a cleanup of dead records.

When to use it
an account is marked as closed in your accounting app and should disappear from the sales view too.
Watch out
Make cannot undo the deletion, so guard the module with a filter on a clear condition.
SharpSpring8

Delete an Opportunity

Action

In MakeDeletes an opportunity from your account.

Drops a deal from the SharpSpring pipeline, so forecasts stop counting something that will never close.

When to use it
a duplicate deal was opened by two scenarios and one of them must go, identified by its ID.
Watch out
the deal is gone for good; if you only need it out of sight, updating it with Update an Opportunity is the safer route.
SharpSpring9

Get a Campaign

Action

In MakeGets a campaign by ID.

Fetches one campaign by its ID, so later modules can use its details in a message, a report or a decision.

When to use it
another module already gave you a campaign ID and you need the full campaign before going further.
Watch out
without an ID from a previous module, use List Campaigns instead, which returns every campaign.
SharpSpring10

Get a Lead

Action

In MakeGets a lead by ID.

Reads the full record of a single lead by its ID, handy when a trigger or another app only passes the ID along.

When to use it
a support ticket carries the lead ID and your reply should use the lead's latest details from SharpSpring.
Watch out
it needs the exact ID; to find leads by period, Search Leads is the right module.
SharpSpring11

Get an Account

Action

In MakeGets an account by ID.

Pulls one company record by its ID, so a scenario can enrich an invoice, a contract or a notification with account data kept in SharpSpring.

When to use it
an opportunity points to an account and you want the company details before sending a proposal.
Watch out
feed it the ID from a previous module, and read the returned bundle in Run once before mapping it further.
SharpSpring12

Get an Opportunity

Action

In MakeGets an opportunity by ID.

Reads a single deal by its ID, giving later modules its current state rather than the snapshot taken when it was created.

When to use it
before sending a contract, a scenario confirms the deal behind it still exists and reads its latest details.
Watch out
one module call is one operation; skip it if the trigger already brought everything you need.
SharpSpring13

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Sends any request the SharpSpring API accepts, with the connection you already set up, for the jobs none of the 26 ready-made modules covers.

When to use it
you need a SharpSpring object or action that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the SharpSpring API documentation open; test it with Run once and read the response bundle.
SharpSpring14

Update a Campaign

Action

In MakeUpdates an existing campaign.

Changes an existing campaign so SharpSpring reflects what was decided elsewhere, without anyone logging in to edit it.

When to use it
the project behind a campaign is renamed or rescheduled in your planning tool.
Watch out
you need the campaign's ID; keep it from Create a Campaign or find it with List Campaigns earlier in the flow.
SharpSpring15

Update a Lead

Action

In MakeUpdates an existing lead.

Edits a lead already in SharpSpring, so fresh information from another tool lands on the right person instead of a new duplicate.

When to use it
a lead books a meeting in your scheduling app and the SharpSpring record should show it.
Watch out
it acts on one lead per bundle, so get the lead ID from Get a Lead, Search Leads or List Leads earlier in the flow.
SharpSpring16

Update an Account

Action

In MakeUpdates an existing account.

Brings a company record in SharpSpring up to date when the source of truth for that company lives in another system.

When to use it
finance changes a client's billing details in the accounting app and sales should see the same thing.
Watch out
a SharpSpring update does not start Watch Accounts, which only reacts to new accounts, so plan any follow-up in this same scenario.
SharpSpring17

Update an Opportunity

Action

In MakeUpdates an existing opportunity.

Moves a deal forward in SharpSpring from outside, so the pipeline follows what actually happens with the customer.

When to use it
a contract is signed in your e-signature tool and the matching opportunity should reflect the win.
Watch out
the module needs the opportunity ID; store it when the deal is created or retrieve it with List Opportunities.
SharpSpring18

List Accounts

Search

In MakeGets a list of accounts.

Returns your SharpSpring accounts as separate bundles, one per company, ready to be copied, checked or counted by the next modules.

When to use it
you are loading every client company into a shared spreadsheet for the first time.
Watch out
a search can return zero, one or many bundles, and every bundle processed downstream costs operations.
SharpSpring19

List Campaigns

Search

In MakeGets a list of campaigns.

Gets all your SharpSpring campaigns in one step, each campaign becoming its own bundle for the rest of the scenario.

When to use it
a campaign overview for a marketing review, or finding the ID of a campaign before updating it.
Watch out
if you only need one campaign and already have its ID, Get a Campaign is lighter.
SharpSpring20

List Leads

Search

In MakeGets a list of leads.

Returns the leads of your SharpSpring account one bundle at a time, which lets the next modules sort, copy or check each person.

When to use it
a one-off migration of your leads to another tool, or a check for duplicates before creating new ones.
Watch out
on a large database, each lead handled after this module counts as operations, so filter early.
SharpSpring21

List Opportunities

Search

In MakeGets a list of opportunities.

Collects the opportunities of your SharpSpring pipeline as bundles, giving you raw material for a forecast or a pipeline audit.

When to use it
a sales manager wants every deal copied to a reporting sheet to build charts outside the CRM.
Watch out
an empty result simply means zero bundles, and the following modules will not run.
SharpSpring22

Search Leads

Search

In MakeSearches for leads for a specific date range.

Finds the leads that fall within a date range you choose, so you work on one period instead of the whole database.

When to use it
a marketing report on the leads collected during a trade show or a campaign period.
Watch out
like any search, it may return zero, one or many bundles; add an aggregator if you want a single summary row.
Need help

Need help automating SharpSpring with Make?

A person reads every message.

FAQ

SharpSpring and Make: common questions

01Is the SharpSpring Make integration free?
Yes, SharpSpring is a standard app in Make, so you can use it 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) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits per month. Your SharpSpring subscription is separate and billed by SharpSpring.
02What is needed to connect SharpSpring to Make?
You need an active SharpSpring account and an API Key. In Make, add any SharpSpring module, click Create a connection, give the connection a name if you like, then enter the credentials copied from your SharpSpring account or follow the on-screen instructions. The connection is then reused by every SharpSpring module in your scenarios, so this step happens only once per account. If SharpSpring rejects the credentials, copy them again from your SharpSpring account and create a fresh connection.
03Do SharpSpring triggers in Make work in real time?
No. All four SharpSpring triggers, Watch Accounts, Watch Forms, Watch Leads and Watch Opportunities, are scheduled. Make checks SharpSpring on the scenario's schedule, every 15 minutes by default, and picks up what was created since the previous check. On the Free plan, 15 minutes is the shortest interval; paid plans can go down to 1 minute. None of these modules offers an instant, webhook-based version in Make. Keep this in mind for anything urgent: a lead that fills out a form reaches your scenario at the next scheduled check, not the second it arrives.
04What if a SharpSpring module is missing in Make?
It depends on what you need. The 26 modules cover campaigns, leads, accounts and opportunities: create, read, update, delete, list and a date-range search for leads. For anything else the SharpSpring API offers, the Make an API Call module sends the request with your existing connection. You write the request yourself, so the SharpSpring API documentation becomes your reference, and a Run once test shows the response. Test it on a single record first, because every call counts as an operation on your plan.
05Should SharpSpring be automated with Make or n8n?
It depends on your criteria. Make gives you 26 SharpSpring modules ready to configure, a visual editor and Make an API Call for the gaps, and SharpSpring works from the Free plan. SharpSpring may also be available as an n8n node, so check the node list there if your team already runs n8n. Compare both on the modules you actually need rather than on the brand, and stick with the tool your team already knows.