- Home
- Resources
- Integrations
- Salesforge
Salesforge Make integrationAutomate Salesforge with Make.
Every reply, bounce or click in your Salesforge campaigns can start an automation. The Salesforge Make integration gives you 10 modules: 9 triggers and 1 action. This guide shows sales and ops teams how to connect the account, build a first scenario and pick the right trigger.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Salesforge Make integration do for your outreach?
The Salesforge Make integration links your Salesforge account to Make so that what happens in your email campaigns can start a scenario, the automation you build in Make as a chain of modules. A module is one brick of that chain. Here, 9 of them watch your campaigns and 1 updates the label of a thread.
Route interested prospects faster. Watch positive reply picks up the answers flagged as positive, and Update a Thread Label tags the conversation so your team knows which thread to open first. The same trigger can feed a CRM or a chat tool with a module from another app.
Keep your lists clean. Watch email bounce and Watch contact unsubscribed tell you which addresses should stop receiving anything. Send them to a spreadsheet or to the tool that holds your contacts, and nobody on the team has to check by hand. The Airtable Make integration is one place to store them.
Spot engagement before the reply. Watch email opened and Watch link clicked show which prospects read your message or visited your link, so a rep can follow up while the topic is still fresh.
What Make does not do here: the Make documentation does not state the trigger type, but the names and the absence of a webhook step point to 9 scheduled triggers: Make checks Salesforge on the scenario's schedule instead of hearing about events the moment they happen. There is only one action, and no Make an API Call module to reach the rest of the Salesforge API. The Make documentation for this app is also flagged as AI-generated, so check anything critical against Salesforge itself.
Choosing a tool? The n8n vs Make comparison lays out the criteria, and the Make pricing page explains how operations are counted.
How do you connect Salesforge to Make?
- 01
Copy your API key in Salesforge
You need an active Salesforge account. Open the Settings page, go to the API or API Access section, and copy the API key shown on screen. Keep it at hand for the next step.
- 02
Add a Salesforge module and create the connection
In your Make scenario, add any Salesforge module and click Create a connection. A connection is your Salesforge account linked to Make once, then reused by every Salesforge module. The Connection name field is optional.
- 03
Paste the key and save
Paste the API key you copied, or follow the instructions Make shows on screen, then confirm. Once the connection works, Make can list what it reads from your account when you fill the module fields.
Your first scenario: tag every positive reply
GoalWhen a prospect answers positively in Salesforge, Make updates the label of that thread so it stands out for your team.
- 01
Create the scenario
From the Scenarios page, create a new scenario and click the + in the middle of the canvas to add the first module.
- 02
Pick Watch positive reply
Search for Salesforge, choose Watch positive reply and select your connection, or click Create a connection if this is your first Salesforge module.
- 03
Add Update a Thread Label
Click the + on the right of the trigger and add Update a Thread Label. Map the thread from the trigger's output and choose the label from what Make lists.
- 04
Test with Run once
Click Run once. Make runs the scenario one time and shows each bundle, the item passed from one module to the next, here one reply. Check that the right thread got its label.
- 05
Set the schedule and switch it on
Open the clock on the first module: a new scenario checks every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan. Then switch the scenario on.
The 9 Salesforge triggers and when to pick each
9 modules start a scenario when something happens in Salesforge. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Salesforge as soon as it happens.
Watch contact unsubscribed
triggerIn the docs onlyHands you every contact who unsubscribed from your Salesforge emails, so the opt-out can travel to the other tools that still hold that person.
Watch email bounce
triggerIn the docs onlyBrings each bounced email back into Make, which gives you a clean list of addresses that did not receive your message.
Watch email opened
triggerIn the docs onlyTells your scenario when a prospect opened one of your Salesforge emails, which is often the first sign of interest you get.
Watch email replied
triggerIn the docs onlyCollects every reply to your Salesforge emails, whatever its tone, so no answer sits unnoticed in an inbox.
Watch email sent
triggerIn the docs onlyGives you a trace of each email Salesforge sends, useful when another tool has to know that a prospect has been contacted.
Watch label changed
triggerIn the docs onlyReacts when the label of a thread changes in Salesforge, which turns your own sorting into a signal other tools can follow.
Watch link clicked
triggerIn the docs onlyTells you when a prospect clicked a link in one of your Salesforge emails, a stronger hint of interest than an open.
Watch negative reply
triggerIn the docs onlyIsolates the replies flagged as negative, so a clear no can close the loop in your other tools instead of lingering as an open lead.
Watch positive reply
triggerIn the docs onlyBrings you the replies Salesforge flags as positive, which are usually the conversations worth answering first.
The Salesforge action
Salesforge gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.
Update a Thread Label
ActionIn the docs onlyChanges the label of a Salesforge thread from Make, so the sorting your team relies on happens without anyone opening the inbox.
Need help automating Salesforge with Make?
A person reads every message.