Resources · Make integration

SharePass Make integrationAutomate SharePass with Make.

Need a password or a secret handed over without anyone typing it into a chat? The SharePass Make integration gives you 13 action modules. This guide shows how to link your account, build a first scenario and pick the right module for each job.

Try the SharePass integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SharePass Make integration do for you?

The SharePass Make integration lets a Make scenario (the automation you build, a chain of steps) work on your SharePass account without code. All 13 modules are actions: they create, read, lock or delete secrets. None of them watches SharePass, so the scenario starts from another app or from a schedule.

Credentials for a new hire. When HR adds someone in another app, Generate a password produces a password and Create a secret wraps it in a SharePass secret, so the login never travels in plain text.

Consistent secrets for every client. Support teams that always send the same kind of access can call Get templates once, then use Create a secret from a template so each secret follows the same settings.

Cleanup when a project closes. Update a secret lock state, Erase secret content and Delete a secret let a scenario shut access down as soon as a ticket or a deal is marked done elsewhere.

One honest limit: the Make documentation for SharePass is thin. It states that there is not enough public information about the app to document it fully, so this page names the modules and when to reach for them, not their fields. When a module is missing, Make an API call covers the rest with the same connection. Before building, the Make review helps you judge the tool, and Make pricing explains how operations are counted. If you are still weighing tools, read n8n vs Make.

Connect

How do you connect SharePass to Make?

  1. 01

    Add a SharePass module

    In your scenario, click the +, search for SharePass and pick any module, for example Get user details. Then click Create a connection. A connection is your SharePass account linked to Make once, and every SharePass module reuses it.

  2. 02

    Name it and authorize

    Give the connection a name you will recognize later, such as the team that owns the account. Then either authorize Make on the SharePass page that opens, or paste the key SharePass gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. To be sure the link works, keep Get user details as the only module and click Run once: if your account details come back, the connection is ready for the rest of the scenario.

First scenario

Your first scenario: send a new password as a SharePass secret

GoalWhen another app records a new team member, Make generates a password and stores it in a SharePass secret.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. SharePass has no trigger, so the first module comes from the app where new people appear, like your form tool or HR app.

  2. 02

    Add Generate a password

    Click the + on the right of that first module, search for SharePass and choose Generate a password. Pick your connection or create it here, then fill in what the module asks.

  3. 03

    Wrap it in a secret

    Add Create a secret next. Map the password from the previous module into the secret content, so the value passes from one bundle (one item moving between modules) to the next without anyone copying it.

  4. 04

    Test with Run once

    Click Run once, then trigger a test entry in your first app. Read the bundles each module received and check that a secret was created in SharePass.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default for a new scenario) and switch the scenario on. Each module run counts as one operation on your Make plan.

Modules

What the SharePass modules do

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

SharePass1

Create a secret

ActionIn the docs only

You get a new SharePass secret built from data your scenario already holds, such as a login a previous step produced. It is the core module of most SharePass scenarios.

When to use it
a customer account is opened in your CRM and its first credentials must reach the customer safely.
Watch out
the Make docs describe no fields here, so open the module and map only what it lists.
SharePass2

Create a secret from a template

ActionIn the docs only

This one gives you a secret that follows a template saved in SharePass, so every secret of the same kind looks and behaves alike without setting it up again.

When to use it
your support desk sends the same kind of access to many clients and wants one standard.
Watch out
the template must exist first; Get templates shows which ones your account can use.
SharePass3

Delete a secret

ActionIn the docs only

With this module a secret disappears from SharePass once a scenario decides it is no longer needed. It keeps your account tidy without a manual pass through the list.

When to use it
a contract ends in your billing tool and the access tied to it should vanish too.
Watch out
treat a delete as final, since the docs mention no way back, and test it with Run once on a dummy secret first.
SharePass4

Delete secret attributes

ActionIn the docs only

Here you remove selected attributes from a secret while keeping the secret itself. The module name is all the documentation offers, so check in the module which attributes it lets you pick.

When to use it
part of a secret is outdated but the rest must stay, rather than rebuilding it with Create a secret.
Watch out
run it on a test secret before pointing it at real ones.
SharePass5

Erase secret content

ActionIn the docs only

Erasing the content leaves you with an empty secret: the sensitive value goes, the secret record can stay. That differs from Delete a secret, which removes the whole thing.

When to use it
a password was rotated elsewhere and the old value should no longer be readable.
Watch out
treat it as final; nothing in the docs says the content can be restored.
SharePass6

Generate a password

ActionIn the docs only

Your scenario gets a fresh password as data it can pass to the next module, with no one inventing it by hand. Pair it with Create a secret to deliver it.

When to use it
a new tool account is opened for a colleague and needs an initial password.
Watch out
the generated value lives in the bundle, so avoid sending it on to modules that store plain text.
SharePass7

Get labels

ActionIn the docs only

This module hands your scenario the labels available in your SharePass account, which you can then map into other steps instead of typing them.

When to use it
a scenario must file each new secret under the right label chosen from data in another app.
Watch out
if the list comes back as several bundles, each one runs the following modules and uses operations.
SharePass8

Get secret details

ActionIn the docs only

Reading one secret gives your scenario its details, so a later step can decide what to do: lock it, erase it or report on it.

When to use it
before a cleanup action, to check a secret is really the one tied to the closed ticket.
Watch out
the module has to know which secret to read, so expect to map it from the step that created it.
SharePass9

Get templates

ActionIn the docs only

You see the templates your SharePass account holds, ready to feed into Create a secret from a template without looking them up in the app.

When to use it
while building a scenario, to find the right template, or when the template depends on the client type.
Watch out
run it alone with Run once first and read the bundles to learn what it returns.
SharePass10

Get user details

ActionIn the docs only

This returns details about the SharePass user behind your connection, which makes it a simple way to confirm the connection works.

When to use it
right after creating the connection, or at the start of a scenario shared by several teams, to know which account it runs on.
Watch out
it covers the connected user, not every member of your organization.
SharePass11

Make an API call

ActionIn the docs only

When no listed module does what you need, this one lets your scenario call any endpoint of the SharePass API with the connection you already set up.

When to use it
an action exists in SharePass but not among the other twelve modules.
Watch out
you write the request yourself, so keep the SharePass API reference open, since the Make docs do not describe it.
SharePass12

Manage an API key

ActionIn the docs only

This module lets a scenario act on a SharePass API key as one step of a wider process. Open it to see which actions it offers.

When to use it
key handling is part of a wider process, such as a staff departure checklist run in another app.
Watch out
changing the key your own connection relies on can break every SharePass module in your scenarios.
SharePass13

Update a secret lock state

ActionIn the docs only

Locking or unlocking a secret from a scenario lets you control access without deleting anything. The secret stays, only its availability changes.

When to use it
a deal is paused in your CRM and the shared access should be frozen until it restarts.
Watch out
map the secret identifier carefully, or you may lock the wrong secret.
Need help

Need help automating SharePass with Make?

A person reads every message.

FAQ

SharePass and Make: common questions

01Is the SharePass Make integration free?
Yes, SharePass is a standard app, so its modules are available on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of 5 minutes at most, 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 allow 40 minutes per run. Usage is counted in operations, one per module run. Your SharePass subscription is a separate matter.
02What do you need to connect SharePass to Make?
A SharePass account and a Make account. The Make documentation lists no prerequisites and no official steps for SharePass, so the connection follows the generic path: add a SharePass module, click Create a connection, optionally give it a name, then authorize Make on the SharePass page or paste the key SharePass provides, and click Save. Running Get user details once is a quick check that the connection works before you build the rest.
03Can a SharePass scenario start in real time?
Not from SharePass itself, because the app has no trigger module. All 13 modules are actions. A scenario therefore starts in one of two ways: a trigger from another app, such as a form or a CRM, placed first in the flow, or a schedule set on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that interval. Whether the first app reacts instantly depends on that app, not on SharePass.
04What if a SharePass module is missing in Make?
Use Make an API call. It reaches any endpoint of the SharePass API with the same connection, so an action that none of the other modules covers can still run in your scenario. Keep in mind that the Make documentation for SharePass is limited: it says there is not enough public information to document the app fully. You will need the SharePass API reference to write the request, and a test with Run once before switching the scenario on.
05Should you use Make or n8n with SharePass?
It depends on your criteria, and this page only covers the Make side. In Make, SharePass comes with 13 action modules, Make an API call included, and it runs on the Free plan. Many apps also have an n8n node; check whether SharePass has one before choosing. Compare the modules each tool offers for your use case, how your team already works, and how each counts usage. The comparison linked earlier on this page goes through those points in detail.
Same platform

Other docs you might need on this stack.

Browse all integrations