Connecting services
Under Connections you store the accounts your agents and workflows work with, for example a mailbox. A connection applies only to you and only in one workspace.
Connect a service
- Open Connections in the user menu.
- Find the service in the tab Services.
- Click Connect. A window of the provider opens.
- Confirm the access there. The window then closes by itself.
Each service is connected separately and has its own rights. Gmail, Google Calendar and Google Drive are three services, although there is one Google login behind them.
Connect with an API key
You connect Lusha and Shopify with an API key. The same applies to Stripe as long as no Stripe app is stored on the lowcloud server.
For these services, Connect opens a dialog with the field API key instead of the sign-in window. For Shopify there is also the field Shop domain, for example myshop.myshopify.com. The help text below the field says where you get the key and which rights it needs.
lowcloud checks the key with the provider before it saves it. If it does not fit, "[Service] rejected the key. Check it and try again." appears.
Manage accounts
A service can hold any number of accounts. Click the service and then Connect another account at the bottom. Each account is a row of its own under Connected accounts, with the identity at the provider and the date.
The … menu of an account row offers:
- Rename: sets a display name. If you leave it empty, the identity of the account appears again.
- Re-authorise: runs the consent at the provider again, for instance after new rights.
- Manage at [service]: leads to the provider's settings page. Currently this exists only for GitHub.
- Set as default: marks the account with Default.
- Test: checks the connection.
- Delete: removes this one account, without confirmation.
If no account is fixed for a run, it takes the account marked Default, otherwise the one connected most recently.
If you sign in with a different account during Re-authorise, a second connection is created. Existing assignments keep pointing to the old one. For GitHub, Re-authorise only renews the access of the installations already connected in this workspace.
Test a connection
Test fetches real data from the provider, by the same route a run takes. On success, lowcloud shows one line about the account, for instance the email address. If the test fails, "Connection test failed" appears with the provider's error text.
Disconnect a service
Disconnect on the service deletes all accounts of this service that you connected in this workspace. The same account in another workspace stays.
The workflow can be activated again only once an account is set. So before disconnecting, connect the replacement account and set it in the workflow.
Available services
The catalog contains more than 20 services with more than 300 functions in total.
| Service | What for | Triggers |
|---|---|---|
| Gmail | Read, answer and send emails | yes |
| Google Calendar | Read, create and change events | yes |
| Google Drive | can be connected, but has no functions | no |
| Google Sheets | Read and write spreadsheets that you select for lowcloud | no |
| Google Search Console | Evaluate search data of verified properties | no |
| Outlook Mail | Read and send emails | yes |
| Outlook Calendar | Read, create and change events | no |
| OneDrive | Read and store files in the personal OneDrive | no |
| SharePoint | Search sites, read and store files | no |
| Microsoft Teams | Read and send messages, retrieve meeting transcripts | yes |
| Microsoft To Do | Maintain task lists, tasks and checklists | no |
| IMAP mailbox | Read and send emails in a mailbox without a connector of its own | yes |
| Notion | Pages and databases of a Notion workspace | no |
| Airtable | Read and write bases, tables and records | yes |
| Pipedrive | CRM: contacts, deals and activities | yes |
| GitHub | Repositories, issues and pull requests | yes |
| HubSpot | CRM: contacts, companies and deals | no |
| Apollo | Prospecting plus your own Apollo CRM | no |
| Lusha | Enrich business contacts and company data | no |
| Stripe | Customers, payments, subscriptions and invoices | yes |
| Shopify | Orders and products in your own shop | yes |
Google Drive has no functions in the catalog yet. For working with files, use SharePoint or OneDrive.
Available soon
At the end of the list, greyed out, are the services under Available soon, marked Preview. You cannot connect them.
Attio, Confluence, Jira and Slack are always there. Google Ads is there as well. All five have no functions. In addition there is every service for which no access is stored on the lowcloud server yet.
Reading and writing
If you click a service, Access rights and functions lists every function that lowcloud can perform there. Other functions of the service are not available. For services with an API key, the functions are further limited to what your key allows.
Each function carries one of two labels:
- Reads: fetches data. The function runs straight through in the run.
- Writes: changes or sends something in the target system. The call stops by default and waits for your approval.
The approval for Writes is a default. Per agent and per step you can switch it off for an individual tool, and lowcloud then asks once more. Conversely, you can also make a reading function require approval. How approvals work is described under Approvals and questions.
Triggers
For services with triggers, the block Triggers is above the list of functions. It shows the events that can start a workflow by themselves. The events of all services are listed under Triggers.
The triggers poll the provider at intervals. None uses a webhook (a message the provider sends by itself). So a run starts with a delay.
Special cases for individual services
GitHub
On the first connection you select the account and the repositories on GitHub's installation page. If the GitHub app is already installed on at least one account, you select the GitHub accounts instead. Every ticked account becomes a connection of its own with the repositories that are shared there.
You change repositories later at GitHub via Manage at GitHub. Then you bring the change over to lowcloud with Re-authorise.
Microsoft
You cannot connect Microsoft Teams on your own. Several permissions need the one-time consent of an IT admin of your organisation. Until then the sign-in window reports that this approval is missing. After that you click Connect again. The organisation can additionally switch off meeting transcripts entirely.
Shared Microsoft mailboxes additionally need Exchange rights that only the M365 administration grants: full access for reading and Send as for sending. The consent at Microsoft alone is not enough.
New permissions
When new Microsoft permissions are added, existing connections of that service stop working. Microsoft refuses rights that the stored consent never agreed to. Those affected have to run Re-authorise by hand.
With Google, Airtable and Apollo the connection remains. The new functions answer with a permission error until you have reconnected.
Costs at the provider
At Apollo, six queries cost credits: enriching and fetching people, searching, enriching and fetching companies, and fetching job postings. Each costs one credit or one credit per page. The people search is free. Access to your own Apollo data (contacts, deals, lists, sequences, tasks) is free as well.
At Lusha, matching a list of addresses and reading out the plan and credits are free. Enriching and unlocking cost credits. A hit without a result is charged too.
Credentials
Access tokens, refresh tokens and pasted API keys are stored encrypted in the database. The browser receives only the account name, display name and date. No secret leaves the server.
Tokens are renewed automatically shortly before they expire. If that fails, the run shows an error such as "Connection not found. Reconnect under /connections". Then you connect the service again.
Tools without a connection
Web search and Read web page run on lowcloud's access. Web search searches the web. Read web page reads a page as text, including YouTube transcripts. In workflows, both are in the group Web. On an agent, you switch them on in the group Web access with Web search and Web pages & files. Neither appears under Connections, and neither costs you anything at the provider.
Custom HTTP integrations and MCP servers with the sign-in Shared access carry their credentials themselves and are not on this page either. An MCP server with Own account per person appears as a row in the list of services, and every person signs in there themselves. How to create both is described under Custom integrations and MCP.
Permissions
Everyone in the workspace sees the tab Services. The tabs Custom integrations and MCP servers are visible only to anyone who may build (the role admin, or the former role developer).
Others do not see your connections in their list. The same mailbox in two workspaces gives two separate connections with separate rights.
On this page you cannot hand a connection over to someone. Each person connects their own account. A workflow can, however, be fixed to the account of a particular person. Runs that colleagues start then act through this account. The approval card in the run shows this case.
In a partner's client workspace, the partner decides which services the client's people may connect, see Partner.