Connecting Instantly to Stacktic

For: an Instantly workspace admin. Takes about 5 minutes.

What this integration does

Connecting Instantly lets Stacktic see everyone in your Instantly workspace. When someone leaves, Stacktic can remove their access in one step.

To connect, you create an API key in Instantly. It works like a password for apps. The key belongs to the workspace, not to the person who creates it. That makes it a service credential, so it keeps working even if that person later leaves your team. Stacktic stores the key encrypted and only uses it with your Instantly workspace.

Stacktic needs one value:

Value What it is
API key An Instantly API key, with permission to read and (optionally) manage workspace members.

Before you start

  • You need access to Instantly → Settings → Integrations → API Keys in the workspace you want to connect.
  • Decide whether you want Stacktic to only see your workspace's members for now, or also remove them automatically during offboarding. The scopes you give the key decide this. (A scope is one specific permission.) See Step 1.

Step 1: Create the API key

  1. In Instantly, go to Settings → Integrations → API Keys.
  2. Create a new key and give it these scopes:
    • workspace_members:read: required. This lets Stacktic see who's in the workspace.
    • workspace_members:delete: add this if you want Stacktic to remove people automatically during offboarding. Skip it for now if you only want visibility.
    • workspaces:read: optional. Stacktic only uses it to show your workspace's name on the connection card. The connection works fine without it.
  3. Copy the key. Instantly keys don't expire on their own. The key stays valid until you delete it in Instantly, so there's no rotation schedule to plan around.

Step 2: Connect in Stacktic

In Stacktic, go to Tools → Instantly → Integration. Paste the key into the API key field and click Connect.

Stacktic checks the key against your workspace before saving it. If the key is wrong, expired, or missing a required scope, Stacktic tells you so. It won't save a broken connection.

Step 3: Turn on removal (when you're ready)

Stacktic starts reading your workspace's member list as soon as you connect. Removing members during offboarding is a separate switch. It's off until you turn it on, even if your key already has the workspace_members:delete scope, because removal is destructive.

When you want Stacktic to remove people from Instantly during an offboarding, turn on Automated user removal on the integration.

What "connected" looks like

Once you're connected, Stacktic lists every accepted member of the workspace:

  • Accepted members only: people who've joined, not people who've only been invited. A pending invite doesn't have any access yet, so it isn't shown here.
  • Roles: each person's role (Owner, Admin, Editor, and so on) comes straight from Instantly and is shown next to them.
  • Last active: this column is empty for everyone. Instantly's API doesn't share a last-active date, so Stacktic doesn't have one.

What removal does (and doesn't do)

Removing a member takes them out of the Instantly workspace completely, ending their access to it.

Removal does not:

  • delete their personal Instantly account.
  • change their access to any other Instantly workspace they belong to.

Instantly's workspace Owner can't be removed through this integration. If the person leaving is the workspace's Owner, move ownership to another member in Instantly first. Then Stacktic can remove the original Owner's access on the next offboarding step.

What this doesn't cover

Instantly has Workspace Groups. With them, one admin API key can reach into a separate sub-workspace's data. This integration doesn't follow that path. It only ever sees the single workspace the key belongs to.

If your organization uses Workspace Groups, some people may reach a workspace only that way. They won't appear on this workspace's member list. So not seeing someone here doesn't mean they have no access.

Read-only vs. removal

  • workspace_members:read only: Stacktic shows your Instantly workspace's members next to the rest of your tools. Nothing here can change or delete anything.
  • workspace_members:read + workspace_members:delete, with Automated user removal turned on: Stacktic also removes people during offboarding.

You can start read-only and add the delete scope later. Create a new key with both scopes in Instantly and reconnect with it.

Security notes

  • Least privilege. Give workspace_members:delete only once you're ready for automatic removal. workspace_members:read alone is enough for visibility.
  • Not tied to a person. This is a service credential for the workspace, not a personal login. Someone leaving your team won't break the connection, the way it would with a personal access token.
  • No built-in expiry. Instantly API keys don't expire on their own. Changing the key from time to time is up to you. Delete the old key, create a new one in Instantly, then reconnect in Stacktic with the new value.
  • Stored encrypted. Stacktic keeps only the key, encrypted. It never shows the full key again. You only see its last 4 characters, so you can confirm which key is connected.
  • You can cut it off anytime. Delete the key in Instantly (Settings → Integrations → API Keys) and the connection stops working right away.
  • Needs an active paid plan. Instantly blocks member removal on a workspace without an active paid plan. If your plan lapses, reading the member list keeps working (Stacktic just retries later). But removal during offboarding is blocked until the plan is active again.

Troubleshooting

Message in Stacktic Likely cause and fix
"Instantly refused the request (HTTP 401). The API key has most likely been deleted or revoked." The key was deleted or was never valid. Create a new key in Instantly and reconnect.
"Instantly refused the request (HTTP 403)." The key doesn't have the scope this request needs (workspace_members:read or workspace_members:delete). Create a key with the right scopes and reconnect.
Stacktic reports it couldn't reach Instantly right after you tried to connect If your Instantly workspace doesn't have an active paid plan right now, connecting can fail with this general message. The real cause is billing, not the key. Confirm the workspace's plan is active, then reconnect.
Offboarding removal fails: "Instantly does not allow removing a workspace's Owner through this API." You're trying to remove the workspace's Owner. Move ownership to another member in Instantly first, then retry.
Offboarding removal fails: "Instantly requires an active paid plan to remove workspace members." The workspace's plan has lapsed. Removal is blocked until it's active again. Reading the member list still works.
Offboarding removal reports the person isn't found They were already removed from the workspace, or never joined. Stacktic counts this as done. You don't need to do anything.

Frequently asked questions

Does this credential expire? No. Instantly API keys don't expire, and Instantly doesn't document any rotation. The key is valid until you delete it in Instantly.

Is this tied to whoever creates the key? No. It's a service credential for the workspace, not a personal one. The key keeps working even if the person who created it leaves.

Will Stacktic see invites I've sent that haven't been accepted yet? No. Only accepted members show up, because a pending invite doesn't have any access yet.

Can Stacktic invite new people into my Instantly workspace? No. This integration only reads the member list and removes people during offboarding. It doesn't create or invite members.

What if my organization uses Instantly Workspace Groups? Someone who reaches a workspace only through a Workspace Group won't show up on that workspace's member list here. See What this doesn't cover above.

Will connecting remove or change anything right away? No. Connecting only reads your workspace's current member list. Stacktic removes people only during an offboarding, and only after you turn on Automated user removal.

See also

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.