IntegrationsMake

Start a Make scenario on every reply, and send leads back in.

Create an API key, add the GetSales app to a scenario and pick the events. A reply, a hand-off or a website visit starts the scenario, and a GetSales module further on adds people to a table or a workflow.

  • ConnectSettings, API keys
  • DirectionBoth ways
  • Credits0 per event
GetSales to Make

What moves between GetSales and Make: an event such as a reply, a hand-off or a website visit starts a scenario, and Make's actions add a person to a table, add people to a workflow or search people in GetSales.

  1. A reply, a hand-off, a visit to A trigger starts the scenario

    GetSales to Make, as an event

  2. A person in a table to Add a person to a table

    Make to GetSales, skipped if GetSales has them

  3. People in a workflow to Add people to a workflow

    Make to GetSales, the workflow's steps take over

  4. A person found to Search people

    Make reads it from GetSales

What it does

What starts a scenario,
and what Make can do

One trigger for any GetSales event, named triggers for the common ones, four actions and an API call.

Triggers: GetSales to Make

  • Watch events

    Pick the GetSales events you want in one trigger. Make subscribes and unsubscribes for you.

  • Watch replies

    A lead answered on LinkedIn or by email.

  • Watch new tasks

    A task for someone on your team, the AI SDR's hand-offs included.

  • Four more

    Watch conversation state changes, Watch leads leaving workflows, Watch identified website visits, Watch finished imports and searches.

Actions: Make to GetSales

  • Add a person to a table

    From a form, a CRM or a sheet. A person GetSales already has is skipped, not changed.

  • Add people to a workflow

    Pick the workflow and they enter its steps. Anyone already in it is left alone, and your stoplist still holds.

  • Search people

    Look people up in your workspace by an email, a LinkedIn identifier, a search text or a table.

  • Make an API call

    A workspace call the key's permissions allow, with the same connection. Sending and other channel actions are refused.

Not in this version

  • Sending messages

    Make cannot send a LinkedIn message or an email. Add people to a workflow and its steps send.

  • Building workflows or tables

    No module creates or edits a workflow, a table or a column, and an Automation platform key may not. Build them in GetSales.

  • Connection accepted

    No trigger fires when someone accepts a connection request.

  • Updating people

    No module changes the fields of a person already in GetSales: Add a person to a table leaves them as they are.

When it runs

Set it once,
it keeps running

A scenario with GetSales in it runs like any other scenario in Make.

  1. On an event

    The trigger fires when GetSales records the event: a reply lands in Unibox, a task opens, a person leaves a workflow.

  2. In any scenario

    The actions run after any app Make connects, such as a form, a CRM or a spreadsheet.

  3. Then in GetSales

    A person added to a table meets its Auto-run columns, and people added to a workflow start its steps. Nobody has to press run.

What it costs

Nothing
per event

Events, reads and writes move your own data, so GetSales charges no credits for them. What an action starts in GetSales is billed as it is in the app.

What a credit costs
An event sent to Make
0
A person added, found or added to a workflow
0
A column that runs on the new row
Its own rate
AI steps and the AI SDR's work in the workflow
As in the app

Set it up

Connected
in five steps

  1. Create a key

    In GetSales, open Settings, API keys and click Create key. Pick the Automation platform preset, name it Make and copy the secret: it is shown once.

  2. Connect Make

    In a Make scenario, add a GetSales module and create a connection with that key.

  3. Pick the events

    Start the scenario with Watch events or a named trigger such as Watch replies. Make subscribes for you.

  4. Add the actions

    Add a person to a table, add people to a workflow or search people, and map the fields from the modules before.

  5. Run it once

    Run the scenario once to check it, then switch it on.

You need a GetSales user who can manage API keys. A key works for one workspace.

Questions

Make,
your questions

Anything else, ask our AI sales agent.

Talk to AI Sales

Can Make work with LinkedIn and email outreach?

Yes, through GetSales. GetSales runs the outreach: workflows send from your sender profiles on LinkedIn and by email, and the replies land in Unibox. The GetSales app in Make starts a scenario on a reply, a hand-off or another event, and adds people to your tables and workflows from any app Make connects.

Which events can start a scenario?

Watch events takes any event GetSales sends to webhooks, picked from a list. The named triggers cover the common ones: Watch replies, Watch new tasks (it carries the AI SDR's hand-offs), Watch conversation state changes, Watch leads leaving workflows, Watch identified website visits, and Watch finished imports and searches.

Can Make add people to a GetSales workflow?

Yes. Add a person to a table or find one with Search people, then use Add people to a workflow with the workflow picked. They enter its steps as people added by hand do, a person already in the workflow stays as they are, and a person on your stoplist does not enter.

Can I send LinkedIn messages or emails from Make?

Not in this version. Sending stays in GetSales: add the person to a workflow and its steps send from your sender profiles, paced within each account's limits.

What happens when a person is already in GetSales?

Add a person to a table skips them and returns the person GetSales has, so the next module can still add them to a workflow. Their fields are not changed: no module updates a person in this version.

Do I need to set up webhooks in GetSales?

No. The trigger subscribes and unsubscribes for you with the key you connected. You only pick the events.

Does the Make integration cost credits?

Events, reads and writes cost no credits. What an action starts is billed as it is in the app: a column with Auto-run on the new row at its own rate, and the AI work of a workflow step or the AI SDR. Make bills its own usage on your Make plan. What a credit costs is on the pricing page.

Your stack, connected

Every reply, where your scenarios run.

Connect Make once. GetSales events start your scenarios, and Make keeps your tables and workflows filled.

Replies in GetSales. Everything else in Make.