Using Space Connect
Integrations
Link Space to the apps your team already uses (email, Slack, Drive, CRM) so agents can read from them and act in them.
An integration connects Space to an outside app. Once connected, two things become possible:
- Actions: the copilot, an agent, a playbook or an automation can do something in the app: send an email, post to Slack, add a CRM contact.
- Triggers: something happening in the app can start an automation, such as a new email or a Slack mention.
Find them under Explore › Integrations.
What you can connect
| App | Things it can do | Can start an automation when… |
|---|---|---|
| Email (Gmail, Outlook, or any mail server) | Send an email, find emails | A new email arrives |
| Slack | Send a message or reply in a thread, list channels, find a person | A new message, or the app is mentioned |
| Google Drive | Find, list, read, download, create and rename files | A new file appears |
| Dropbox | Find, list, read, download and upload files | A new file appears |
| Google Sheets | Create a spreadsheet, read cells, append rows, update cells | |
| HubSpot | Find, create and update contacts; create deals; add notes | |
| Airtable | Find, read, create and update records | |
| Notion | Search, read pages and databases, create and update pages | A new page in a database |
| Stripe | Customers, payments, invoices, payment links, refunds | A payment succeeded |
| QuickBooks Online | Customers and invoices, email an invoice | A new invoice |
| Google Ads | List accounts, run reports, pause or enable a campaign | |
| X (Twitter) | Post, reply, search, read posts | A new mention |
| Apollo | Search and enrich people and companies, create contacts |
Your organization may have more (or fewer) depending on what your administrators have added.
Connecting an app
Open Integrations. There are two lists:
- Discover: a catalog of apps. A + adds one, and a check mark shows what's already added.
- Yours: the connections you can use. Here you sign in with your own account where the organization lets each person connect their own, and you can test a connection.
Adding one is a short guided dialog: the steps to prepare in the other service, a name, whose account it uses, any secrets, which actions need approval, and then the sign-in (usually one click with Google, Microsoft or the app's own sign-in).
Whose account?
| Setup | What it means |
|---|---|
| One shared account | Everyone's actions go through the same account, such as a shared support mailbox. |
| Each person connects their own | Actions run as you. For email that means your own mailbox. |
If a sign-in stops working (for example, a token was revoked), the connection shows Sign in again.
Approvals for actions
Each action on a connection has an approval setting:
| Setting | Meaning |
|---|---|
| Don't ask | Runs without asking |
| Ask when it leaves the organization | Asks only if it goes outside, for example an email to an outside address |
| Always ask | Always asks. Some actions are always set this way: refunds, posting to X, pausing ad campaigns, overwriting a Drive file |
How asking works depends on where it runs. See Approvals.
Using them
- In chat: just ask. “Send the summary to the #sales channel.” If you have several connections of one kind, the copilot picks, or asks which.
- If it can't: the copilot explains why, such as not available to you (ask an admin), not added yet, or not signed in. It tells you what to do next.
- In a playbook: use a Run › Integration step.
- As a trigger: Triggers › New trigger › App event.
- In Brain: Drive and Dropbox can also be synced into a knowledge base.
Who can use what
An Org Admin decides for each integration whether it's open to everyone or limited to certain groups. A Group Admin can switch an integration off for their group, within what the organization allows. A connection card tells you when something is turned off for you.
Keeping data safe
- Credentials are encrypted and never shown to the AI or in the browser.
- Every action is logged: which app, which action, which connection, who approved. The details of what was sent aren't logged.
- Changes to who can use an integration take effect immediately.
Setting up Slack (for admins)
You'll create a Slack app with a bot token, install it in your workspace and invite it to the channels it should read. For triggers, you either give Slack a web address to send events to, or use Socket Mode, which needs no public web address. The connection dialog lists the exact permissions and steps.