Connecting your systems
Every system SourceLace connects to: which official interface it uses in each one, how people sign in, who sets what up, what people can read and change, what your network needs, and what to do when a connection fails. Start with the table, then follow the system's own page.
Every system SourceLace connects to
One row per connector: the official interface SourceLace uses in that system, how people sign in, what it reads and can change, what your network needs, and its status. The page in the last column has the full setup.
Each connector has one of three labels:
- Verified: tested on a real account. Salesforce, SAP S/4HANA and SuccessFactors (on SAP's public sandbox), Gmail, Google Calendar and Google Drive.
- Available: built on the vendor's published API, and validated in your environment during onboarding.
- Pilot: new or partial, offered to pilot customers. In the System picker on Connections, Pilot connectors are marked "in testing".
Tell support@sourcelace.com before you start with an Available or Pilot connector, so we can help with the first connection.
Changes are always off until a SourceLace admin turns them on for a source and names the objects (see Turning on changes). Every change is shown to the person as a preview first and is made only after they say yes. "Read only" means the connector never changes anything in that system, whatever the settings say.
Network uses three short answers, explained under What your network needs:
- Nothing to open: SourceLace calls the vendor's cloud service over HTTPS. You open no port. Only if you limit that service to known IP addresses do you add SourceLace's.
- Allow SourceLace's IP addresses: the system needs an address on the internet, and its firewall must let SourceLace's outbound IP addresses in.
- SourceLace Agent or SAP BTP: nothing connects in to your network. Either a small agent in your network connects out, or your existing SAP BTP and Cloud Connector carry the calls.
| System | Kind | Connects through | Sign-in | Reads and changes | Network | Status | Setup page |
|---|---|---|---|---|---|---|---|
| Salesforce (Sales and Service Cloud) | salesforce |
Salesforce REST API (SOQL, describe, records) | Personal sign-in | Reads SOQL, schema, records. Changes: create, update, delete | Nothing to open | Verified | Salesforce |
| Salesforce Data 360 (Data Cloud) | data360 |
Salesforce Data 360 Query API, signed in through Salesforce | Personal sign-in | Reads SQL, schema, records. Read only | Nothing to open | Available | Data 360 |
| Salesforce Marketing Cloud Engagement | sfmc |
Marketing Cloud REST API (data extensions, journeys, content, send definitions) | Personal sign-in | Reads data extension rows, schema, journeys, content. Read only | Nothing to open | Pilot | Marketing Cloud |
| SAP S/4HANA | s4hana |
SAP S/4HANA OData APIs on your own system (Cloud Public Edition directly; Private Edition or on-premise through SAP BTP or the SourceLace Agent), or SAP's public demo sandbox | Personal sign-in (sandbox: shared account) | Reads OData. Creates and updates records after approval, never deletes (sandbox: read only) | Public Edition: nothing to open. Private Edition or on-premise: SourceLace Agent or SAP BTP | Pilot on your own system; verified on SAP's public demo sandbox | SAP |
| SAP SuccessFactors | successfactors |
SAP SuccessFactors OData API on SAP's public sandbox | Shared account | Reads OData. Read only | Nothing to open | Verified, on SAP's public demo sandbox only | SAP |
| SAP ECC (on-premise) | ecc |
SAP Gateway OData (V2) services | Personal sign-in | Reads OData. Changes: create, update | SourceLace Agent or SAP BTP | Pilot | SAP ECC |
| SAP Datasphere | datasphere |
SAP Datasphere consumption OData APIs | Personal sign-in | Reads views and analytic models exposed for consumption. Read only | Nothing to open | Pilot | SAP Datasphere |
| HubSpot | hubspot |
HubSpot CRM API (search, objects, properties, owners) | Personal sign-in | Reads CRM search, schema, records. Changes: create, update, delete | Nothing to open | Available | HubSpot |
| Gmail and Google Calendar | google_workspace |
Gmail API and Google Calendar API | Personal sign-in | Reads mail, events, calendars. Changes: email drafts and calendar events, never sends email | Nothing to open | Verified | Mail and calendar |
| Outlook mail and calendar (Microsoft 365) | microsoft365 |
Microsoft Graph | Personal sign-in | Reads mail, events, calendars. Changes: email drafts only, never sends | Nothing to open | Available | Mail and calendar |
| Google Drive | google_drive |
Google Drive API | Personal sign-in | Reads search, folders, file text. Changes: agents save files they made to a folder, where an admin allows it | Nothing to open | Verified | Files |
| SharePoint and OneDrive | microsoft_files |
Microsoft Graph (files, sites and Microsoft Search) | Personal sign-in | Reads search, libraries, file text. Changes: agents save files they made to a folder, where an admin allows it | Nothing to open | Available | Files |
| Amazon S3 | s3 |
Amazon S3 API (ListObjectsV2, GetObject) | Shared account | Reads keys, file text. Read only | Nothing to open | Available | Files |
| Azure Data Lake and Blob Storage | azure_storage |
Azure Blob Storage REST API (List Blobs, Get Blob) | Personal sign-in | Reads file names, folders, file text. Read only | Nothing to open, unless the storage account allows only selected networks | Pilot | Files |
| Google Cloud Storage | gcs |
Cloud Storage JSON API | Personal sign-in | Reads file names, folders, file text. Read only | Nothing to open | Pilot | Files |
| Your own search index (OpenSearch, Elasticsearch, Azure AI Search) | search_index |
The service's search API over HTTPS | Either | Reads search hits, with links back to the files. Read only | Allow SourceLace's IP addresses, if the service limits them | Pilot | Search index |
| Google Sheets | google_sheets |
Google Sheets API | Personal sign-in | Reads one sheet's tabs, named by its link. Changes: add a row, update cells | Nothing to open | Available | Google Sheets |
| ServiceNow | servicenow |
ServiceNow Table API | Personal sign-in | Reads any table the person can read. Changes: create, update | Nothing to open | Available | Service desks |
| Zendesk | zendesk |
Zendesk Support API (Search and Tickets) | Personal sign-in | Reads tickets, users, organizations, groups. Changes: ticket create, update | Nothing to open | Available | Service desks |
| Jira Cloud | jira |
Jira Cloud platform REST API (version 3) | Personal sign-in | Reads issues, projects. Changes: issue create, update, comment | Nothing to open | Available | Service desks |
| Snowflake | snowflake |
Snowflake SQL API | Personal sign-in | Reads SQL. Read only | Nothing to open, unless the account has a network policy | Available | Data platforms |
| Google BigQuery | bigquery |
BigQuery API | Personal sign-in | Reads SQL. Read only | Nothing to open | Available | Data platforms |
| Databricks | databricks |
Databricks SQL Statement Execution API and Unity Catalog API | Personal sign-in | Reads SQL. Read only | Nothing to open | Available | Data platforms |
| Amazon Redshift (provisioned and Serverless) | redshift |
Amazon Redshift Data API | Either | Reads SQL. Read only | Nothing to open, even for a private cluster | Pilot | Data platforms |
| Amazon Athena | athena |
Amazon Athena API, with the AWS Glue Data Catalog | Shared account | Reads SQL. Read only | Nothing to open | Pilot | Data platforms |
| Microsoft Fabric, Azure Synapse | fabric |
The warehouse's SQL endpoint (TDS, TCP port 1433), with Microsoft Entra sign-in | Personal sign-in | Reads SQL (T-SQL). Read only | Allow SourceLace's IP addresses (Synapse firewall) | Pilot | Data platforms |
| Trino, Starburst Enterprise, Starburst Galaxy | trino |
Trino client REST API over HTTPS | Personal sign-in | Reads SQL. Read only | Allow SourceLace's IP addresses | Pilot | Trino and Starburst |
| Lake tables (Iceberg, Delta, Parquet in Amazon S3) | lake |
Amazon S3 API, with AWS Glue Data Catalog or an Iceberg REST catalog | Shared account | Reads SQL over the tables an admin declares. Read only | Nothing to open | Pilot | Lake tables |
| Microsoft Dynamics 365 (Dataverse) | dynamics365 |
Dataverse Web API (OData v4) | Personal sign-in | Reads OData, schema, records. Changes: create, update | Nothing to open | Available | Business apps |
| Microsoft Dynamics 365 Finance and Supply Chain | dynamics365_fo |
OData service of the environment (/data) |
Personal sign-in | Reads OData over data entities, records. No changes | Nothing to open | In testing | Business apps |
| Oracle NetSuite | netsuite |
NetSuite REST web services (SuiteQL and the REST record service) | Personal sign-in | Reads SuiteQL, schema, records. Changes: create, update | Nothing to open | Available | Business apps |
| Gong | gong |
Gong API (version 2) | Shared account | Reads calls, transcripts, users, stats. Read only | Nothing to open | Available | Business apps |
| Gainsight CS | gainsight |
Gainsight's data, CTA and success plan APIs | Shared account (one access key) | Reads companies, CTAs, success plans and other objects. Read only | Allow SourceLace's IP addresses, if Gainsight limits them | Pilot | Customer success platforms |
| ChurnZero | churnzero |
ChurnZero's REST API (OData) | Shared account (one API user and key) | Reads accounts, contacts, churn scores, surveys, tasks and more. Read only | Nothing to open | Pilot | Customer success platforms |
| Flexport | flexport |
Flexport's API (shipments and freight invoices) | Shared account (one API key) | Reads shipments and freight invoices. Read only | Nothing to open | In testing | Logistics |
| Oracle Fusion Cloud (ERP, SCM, HCM) | oracle_fusion |
Oracle Fusion Cloud REST APIs | Personal sign-in | Reads REST resources. Changes: create, update | Nothing to open | Available | Oracle Fusion |
| Workday | workday |
Workday REST API and Workday Query Language (WQL) | Personal sign-in | Reads WQL, REST. Changes: start a business title change | Nothing to open | Available | Workday |
| PostgreSQL, MySQL, MariaDB, SQL Server, Oracle Database | database |
The database's own network protocol, always over TLS | Personal sign-in | Reads SQL. Read only | Allow SourceLace's IP addresses | Available | Databases |
| MongoDB | mongodb |
MongoDB's own network protocol, always over TLS | Personal sign-in | Reads find and read-only pipelines. Read only | Allow SourceLace's IP addresses | Available | Databases |
| Slack | slack |
Slack Web API, with each person's own user token | Personal sign-in | Reads conversations, messages, threads, search, people, files. Changes: post or schedule a message (with files an agent made), create a channel or canvas, add a reaction | Nothing to open | Pilot | Slack and Teams |
| Microsoft Teams | microsoft_teams |
Microsoft Graph (Teams, chats, online meetings) | Personal sign-in | Reads channels, chats, messages, search, people, files, meeting transcripts. Changes: post a message (with a file an agent made, in a channel), create a channel, add a tab, add a reaction | Nothing to open | Pilot | Slack and Teams |
| Health records through FHIR R4 (Epic, Oracle Health, MEDITECH) | fhir |
The EHR's FHIR R4 API, with SMART on FHIR sign-in | Personal sign-in | Reads FHIR search, resources by id. Read only | Allow SourceLace's IP addresses, if the EHR limits them | Pilot; no business associate agreement yet, so test data only | Health records |
| Healthcare claims through a clearinghouse (Stedi, Availity, Optum) | claims |
The clearinghouse's API (eligibility, claim status, remittance) | Shared account (one API key, or one client ID and secret) | Reads eligibility, claim status and remittance (remittance from Stedi and Optum). Read only | Nothing to open | Tested on the vendors' test systems: Stedi eligibility; Availity eligibility and claim status; Optum eligibility, claim status and remittance (sandbox). The rest in testing. No business associate agreement yet, so test data only | Healthcare claims |
| Any REST API, no code | rest |
The API's own REST endpoints, from its OpenAPI document or endpoints an admin lists | Either | Reads the API's GET operations. Changes: only the operations an admin switches on | Allow SourceLace's IP addresses, if the API limits them | Pilot | Any REST or SOAP system |
| Any SOAP web service, no code | soap |
The service's SOAP 1.1 or 1.2 endpoint, from its WSDL | Either | Reads the operations an admin marks as reads. Read only | Allow SourceLace's IP addresses, if the service limits them | Pilot | Any REST or SOAP system |
| Another vendor's MCP server | mcp |
The vendor's MCP server (Streamable HTTP), with only the tools an admin allows | Either | Reads the tools an admin marks as read-only. Changes: only the tools an admin allows, each approved by the person | Allow SourceLace's IP addresses, if the server limits them | Pilot, switched on per organization | Outside MCP servers |
| Your own system, through a connector you build | custom |
The SourceLace connector protocol: signed HTTPS calls to your own web service | Shared account | Reads your connector's own query language. Changes: create, update, delete, if your connector allows them | Allow SourceLace's IP addresses, if your connector limits them | Available | Build your own connector |
A system that is not on the list
The table above lists the systems SourceLace has a ready-made connector for. A system that is not there can usually still be reached, by one of three routes. Pick the first row that fits.
| If the system… | Use | What you need | Status | Page |
|---|---|---|---|---|
| offers its own connection for AI tools (an MCP address) | Another vendor's MCP server | The address and a sign-in; your admin allows only the tools people may use | Pilot | Outside MCP servers |
| has a REST API or a SOAP web service | Any REST API or Any SOAP web service, no code | The API's description (an OpenAPI document or a WSDL) or a few endpoints written by hand, and a sign-in; an admin describes it on Connections | Pilot | Any REST or SOAP system |
| has neither, or needs rules of its own | Your own system, through a connector you build | Your developers write a small web service that follows the connector protocol | Available | Build your own connector |
What you get. People ask questions, SourceLace reads the system as each person where the sign-in is personal, every call is on the audit trail, access by group and data protection rules apply as for any other source, and the system can be one of the systems in a question across several. Changes are off until an admin switches on the operations or tools that may change data, and each one is previewed and approved first.
What is different from a ready-made connector.
- Status. The first two routes are Pilot: offered to pilot customers, and not yet used on a customer's live system.
- Setup is yours. A ready-made connector comes with its sign-in steps and field list. Here your admin describes the system, and the page for the route says exactly what to enter and how to check it.
- Long lists need a hint. A ready-made connector for a database or warehouse asks the system for only the records a question needs. For these routes, your admin can tell SourceLace which of the system's parameters narrows which field (Filters you declare); without that, SourceLace reads the records and filters them itself, which is slower on a long list. SourceLace says when an answer is incomplete because a list was longer than the pages it reads.
- Reads only through safe calls. A REST read is a GET, a SOAP operation must be one your admin marks as a read, and a tool must be one allowed as a read.
What these routes cannot do.
- A system whose only way to read is to send it a request that is not a plain GET, such as running a database query through a web call, cannot be a REST source. If it is a database or data warehouse, use its own connector from the table above instead.
- A system that has no interface for programs, only a web page or a login screen, cannot be reached. Ask the vendor for an API, or build a connector over the data you can export.
- A list that needs a value before it will answer (a customer's invoices, given the customer's id) can be asked about on its own, but is not read as a table in a question across systems unless your admin declares a tested filter that supplies the value.
Not sure which route? Tell your SourceLace contact the system's name and what you want to ask it. For most systems the answer is one of the first two rows.
How connecting works
Connecting a system takes up to three steps, done by different people:
- Once per system, in that system (some systems only): your admin for that system registers SourceLace there, for example an OAuth client in ServiceNow or a security integration in Snowflake. Some systems use an app SourceLace provides instead, which your admin may need to approve or install.
- Once, in SourceLace: a SourceLace admin adds the source on Connections, with that system's options (see Sources).
- Each person, once: they connect the source, from My connections in the SourceLace app or by asking their AI app to connect it. For most systems the system's sign-in page opens; they sign in there with their own login and come back. For a system with a shared account (see below), connecting needs no login. A connect link works once, for 10 minutes.
From then on, for a system with a personal sign-in, every request runs with that person's own sign-in, so the system's own permissions decide what they see and change. SourceLace keeps each person's sign-in encrypted with your organization's key and never shows it to anyone, including admins. A few systems use a shared account instead; How people sign in to each system lists them.
Your sources page
My connections in the SourceLace app has the same layout as Connections: a list at the left, filters above a table, and one line for each connection you may use. It shows, in one place, whether you are signed in, whether the connection is working for you right now, and what you used in the last 24 hours. The connections that still need your sign-in come first, so you see what to connect at the top. At the top, a slim bar shows whether the AI assistant is ready, which model it uses and how much of this month's included AI use is used (the ⓘ has the rest: renewal, prepaid and extra use), with a Usage details link for admins.
The list at the left has Needs you (connections that need your sign-in or have a problem), All connections, and then the categories you have a connection in (CRM and sales, Databases and so on), each with how many.
Each line shows:
- Connection: the system's logo, the connection's label (click it to open its details; a long label is cut short, and hovering shows all of it) and, at the right edge of the cell, a ⋯ menu with its actions.
- System: the specific system, such as Salesforce or PostgreSQL.
- Plan: the plan level of the system (Standard, Business or Enterprise).
- Status: Connected (you have signed in, and SourceLace works with your access; hover it to see which account you are signed in as), Needs sign-in (you have not connected it yet, with a Connect button right beside it), or Last test failed (the last connection test your admin ran on it failed; your admin fixes the source and you have nothing to do).
- Last 24 hours and Last used: how many of your calls to it worked or failed, and when you last used it.
- Access: how you sign in (a personal sign-in, or a shared account your admin set up for everyone) and whether it is read only or can make approved changes.
The ⋯ menu has Details, Connect (when you need to sign in), Favourite folders (storage systems), Copy source ID and, under a thin line, Disconnect… (for a connection you signed in to with your own login). A connection that uses a shared account has no Disconnect: it is the account your admin set up for everyone, so the menu says "Uses the account your admin set up. Only an admin can change it." A shared account you have not connected yet still has Connect, which needs no login: one press and it is yours to use.
Above the table, Plan level shows All, Standard, Business or Enterprise connections only, each with how many; hover its heading's ⓘ for what the levels mean. Search finds a connection by its name, source ID, description or system. Status shows only Connected, Needs sign-in or Problems (the last connection test failed, or calls in the last 24 hours failed). System lists only the systems you have a connection of in the list item and plan level you chose, with how many in brackets, and goes back to All systems if the one you chose is no longer in the list. Connections that need your sign-in (or have a problem) come first, one line each; the connected ones below them are grouped by system, and a system with two or more of them gets a heading you can fold. A Shared account you have not used yet says Not connected yet: press Connect once, with no login page. Click a column heading to sort by it, and again to turn the order round (on a phone, use Sort by). Like the Agents list, the table can be resized and rearranged: drag a column heading's edge, and use Columns to move or hide a column. On a phone each connection is a card. Click a connection's name, or Details in its menu, to open a panel with its source ID and Copy button, last 24 hours, last use, how you sign in, its access, its category, its favourite folders (storage systems) and Connect or Disconnect where they apply. SourceLace remembers, in your browser only, which list item, plan level and sort you used last, so the page opens the way you left it; nothing about your connections is stored there.
The old Connection status page is part of this page now, and its address still opens it.
Amazon S3, Azure Storage and Google Cloud Storage sources also have Favourite folders: folders your searches look in first, because searching inside one folder is faster. See Finding files faster. An admin also chooses How this source is searched: names only (the default), or names and file contents in the folders the admin allows. See How S3, Azure Storage and Google Cloud Storage are searched.
Choosing a source from a list
Wherever a page asks you to choose a source (for example when you set up matching in Business setup), the box shows ten sources at a time, the ones you can use now first and then those that still need your sign-in, each marked needs sign in so you can see why (or last check failed when your admin's last test of the connection failed). A line under the list says how many there are, such as Showing 10 of 24. Type a few letters to narrow the list, or press Show more to add the next sources, up to 200; with more than that, type to narrow it. Press the down arrow in the search box to move into the list, then the arrow keys to move through it and Enter to choose one. Escape closes it. On admin pages the list can offer all of the organization's sources; everywhere else it offers only the sources you may use.
Your own accounts
My accounts, at the bottom of My connections, is where you add an extra account of your own, without an admin, once your organization's admin has turned personal accounts on (until then the panel says "Your organization has not turned on personal accounts" and whom to ask): a second Gmail or Outlook mailbox, a personal Google Drive, your own SharePoint or OneDrive, or Google Sheets of your own. Only you can see and use an account you add there; nobody else in your organization is shown it, and the AI apps of other people cannot reach it.
What you can add:
- a system your organization already uses (an admin has added a connection of it on Connections) and that your admin lets people add their own accounts of, under Personal accounts on Connections. Systems you cannot add are greyed, with the reason;
- only systems where each person signs in with their own account and that are on the Standard connector class: Gmail and Google Calendar, Outlook (Microsoft 365), Google Drive, SharePoint and OneDrive, and Google Sheets. Business and Enterprise systems such as Salesforce, SAP or Snowflake are never added this way;
- up to the number your organization allows (2 of 3 used says where you stand). Your admin can change it, or switch personal accounts off for everyone or for a group.
To add one: click Add an account, pick the system, give it a label that tells it from your other sources ("Personal Gmail", "Travel mail") and, if you like, a line about what it is. Add and sign in opens the system's own sign-in page in a new tab, as Connect does: sign in with the account you want there and come back. The account then appears among your sources, marked Your own account, and your AI sees its label and description like any source, so it can name the account it used, or ask which you mean when a question could mean more than one. You can Sign out of it, Edit its label and description, or Remove it (which forgets your sign-in to it) at any time.
Your organization's rules still apply to your own accounts: if your groups may not use a system, you cannot add an account of it either, and your organization's data protection rules for that system apply to what comes back. Changes through your own account (a mail draft, a sheet row) are allowed only if your admin turned that on, and each one is confirmed as usual. Your admin can see how many personal accounts exist and can revoke yours; when you leave the organization, your accounts and sign-ins are removed with your access.
Message queues for agent triggers
A message queue is not a source that agents query. It is a connection an agent can start from: each message on the queue you choose starts the agent. Today the supported services are Amazon SQS, Google Pub/Sub, Apache Kafka and brokers that speak AMQP 1.0 (Azure Service Bus, ActiveMQ and Artemis, Solace, RabbitMQ 4, IBM MQ's AMQP channel and most JMS brokers), and IBM MQ inside your own network through the on-site SourceLace Agent.
An admin adds each connection once, on Connections, under Message queues (shown when starting agents from message queues is switched on for your organization):
- Choose Add a message queue, give it a name people will recognise, and choose its type.
- Fill in what that type asks for, such as the AWS region and how SourceLace signs in to AWS: access keys that may read the queues, or an IAM role SourceLace assumes, so no keys leave your account (its trust policy names the AWS identity SourceLace support gives you and requires your organization's external ID, the same one your Amazon S3 sources use; Test connection names it while the role refuses). Or the Google Cloud project and the JSON key of a service account that may read its subscriptions (the Pub/Sub Subscriber role, and Pub/Sub Viewer to choose subscriptions from a list), or a Kafka cluster's bootstrap servers and how SourceLace signs in to it (SASL/SCRAM, SASL/PLAIN or a client certificate; the connection always uses TLS). For Kafka, allow SourceLace to read the topics and to use consumer groups whose names start with
sourcelace.(or the prefix you choose). For an AMQP 1.0 broker, give its address and a user name and password, an Azure Service Bus shared access policy with the Listen right, or a client certificate; the connection always uses TLS. Agents then name the queue's address exactly as the broker shows it, such asorders,orders-topic/Subscriptions/sourcelaceon Azure Service Bus, or/queues/orderson RabbitMQ 4. For a broker inside your network, choose Through the on-site SourceLace Agent and type the agent's id; the queues it may read are set in the agent's own configuration, and agents choose from that list. Keys and other secrets are stored encrypted for your organization and are never shown again. - Save, then choose Test connection. SourceLace signs in and says whether it works, or what to fix, without ever repeating a key.
To rotate a key, choose Edit and type only the new one: a secret left empty keeps the saved one, and the agents that start from the connection carry on. The type of a saved connection stays the same. A connection cannot be removed while agents start from it. Adding, changing, testing and removing a connection are recorded in the audit trail, without any key.
See Start agents from your message queues.
The redirect URL
Systems that use OAuth sign-in ask for the address they send people back to after they sign in. For SourceLace on this server it is:
https://mcp.sourcelace.ai/connect/callback
Register exactly this address (with https, and no slash at the end) wherever a setup page asks for a redirect URL, callback URL or redirect URI for connecting a source. Single sign-on to SourceLace itself uses a different address, given on the Single sign-on page.
Add a source, step by step
These steps are the same for every system. The system's own page says what to do in that system first, and which options to fill in.
- Do the steps for your admin in that system, from its setup page (for example register an OAuth client, or create a read-only login). Write down what the page tells you to copy, such as a client ID.
- In the SourceLace app, open Connections and click Add a source. This opens the Add a source page, which has three steps at the top: Choose the system, Connection details and Test and save.
- Step 1, Choose the system: type part of a system's name in the search box (it searches every system), or pick a category in the list at the left (CRM and sales, ERP and finance, HR, Service and support, Collaboration and email, Files and storage, Data warehouses and lakes, Databases, Healthcare, and Custom and other; All systems shows everything, and each category shows how many systems it has). All, Standard, Business and Enterprise show only the systems of one plan level, and Sort lists them A to Z or with the systems you already have first. Each system is a small tile with its logo, name and plan level, a lock when your plan does not include it (hover for the reason), In testing when it is a pilot connector, and how many connections you already have of it. A connector that serves several systems lists each one by name (PostgreSQL, MySQL, SQL Server and Oracle Database; Epic, Oracle Health and MEDITECH), so what you pick is what everyone sees afterwards. Click a tile and the panel at the right shows How people sign in (Personal sign-in or Shared account; for a system where you choose, both), what adding it uses on your plan, Before you add it with links to the setup guide, the redirect URL and the network needs, and Start from an existing connection when you already have one of that system (its settings are copied, never its secrets). Click Continue. + Add another <system> on a system's heading on Connections opens this page with the system already chosen, and Add another <system> like this (in a connection's ⋯ menu or its details) also starts from that connection's settings. The browser's Back button goes back to this step, and Choose a different system on the next step keeps the label and description you already typed. Typing in the search box looks at every system, whichever category is open.
- Step 2, Connection details: this is the form. Label people see: such as "Corvanta Salesforce" or "Sales sandbox". You can change it at any time.
- What it is, in a few words (optional): a line that tells this connection from others of the same system, which people and their AI see.
- Short name: suggested from the label (
sales-sandbox) and yours to change until you save. The connection ID becomeskind:name, such assalesforce:sales-sandbox, and stays fixed afterwards. A taken name is flagged as you type. - Fill in the options the system's page lists. Paste secrets (client secrets, keys, passwords) here, never into a chat. After saving, a secret shows only as
(saved). An option that is a list of names (S3 buckets, SAP services, SOAP operations) is a small table: type a name and press Enter or Add, or paste a whole list separated by commas, spaces or new lines. Each name has a Remove button, a Search the list box appears once the list is long, and where the system limits the list a line such as "11 of 42 added" shows how many fit. A name the system would refuse is marked in red before you save. - Leave Allow changes off for a first test. To allow changes later, turn it on and list the objects under Objects that can be changed.
- Click Add source. Step 3, Test and save confirms it is saved. For a REST, SOAP or outside MCP server source, click Test connection there (or later in the connection's details or ⋯ menu on Connections) to check it before people connect.
- Each person then opens My connections and clicks Connect on the connection. What happens next depends on the system: usually its own sign-in page opens, they sign in and come back. Databases, MongoDB and Trino with passwords open SourceLace's own sign-in form for the person's own login. Shared accounts, SAP ECC through the agent, and Amazon Redshift need nothing typed. For Gong, only a Gong technical admin can approve the sign-in (see Gong).
- Ask the first test question from the system's page, in the SourceLace app or in your AI app.
You can also add a source from chat, such as: "Add a SourceLace source salesforce:prod, kind salesforce, label Corvanta Salesforce, login URL https://corvanta.my.salesforce.com". Type secrets on Connections instead.
What your network needs
SourceLace's cloud calls your systems from its own servers, over HTTPS or, for databases, over the database's own protocol with TLS. Where it must reach a system you run, you let in only SourceLace's outbound IP addresses, never the whole internet.
- Cloud services (Salesforce, HubSpot, Google, Microsoft, ServiceNow, Zendesk, Jira, Snowflake, BigQuery, Databricks, NetSuite, Gong, Gainsight, ChurnZero, Flexport, Stedi, Oracle Fusion, Workday, Slack, SAP Datasphere, Amazon Web Services and the like): nothing to open. If you limit a service to known IP addresses (for example a Snowflake network policy, or an Azure storage account that allows only selected networks), add SourceLace's outbound IP addresses to that list.
- Systems you run (databases, MongoDB, Trino, Fabric and Synapse firewalls, REST and SOAP APIs, your own connector, an EHR's FHIR server): they need an address on the internet, and their firewall must let in SourceLace's outbound IP addresses, and nothing else from the internet. SourceLace's cloud refuses private addresses (such as 10.x, 172.16–31.x, 192.168.x), so that no organization can point it at another's internal systems.
- Systems on a private network: for AI agents, a SourceLace Runner in your network can reach private addresses (Enterprise plan only, on request). For SAP ECC, use the SourceLace Agent or SAP BTP (below).
- SAP ECC: reached only through the SourceLace Agent (it connects out to SourceLace on port 443) or through your own SAP BTP and Cloud Connector. See SAP ECC.
- Amazon Redshift: reached through the Redshift Data API, so a private cluster works with no network path to it.
Ask support@sourcelace.com for the current list of SourceLace's outbound IP addresses.
How people sign in to each system
Every source is one of two kinds, and SourceLace shows which on Connections, when an admin adds a source, and on My connections. AI apps see it too, in each source's sign_in.
- Personal sign-in: each person signs in with their own account, so the system applies its own permissions to what they see and change. Two people can get different answers to the same question.
- Shared account: everyone uses one account, key or role that an admin set up for the source. SourceLace's access by group, read rules (which rows each group sees) and data protection rules still limit what each person sees, but the system itself cannot tell people apart, so its own per-person permissions do not apply. Add such a source only where everyone who may use it may see what that account sees, and narrow who can use it with groups.
- Either: the admin chooses for each source, and the app explains the choice before saving.
| System | Kind | Sign-in | What decides it |
|---|---|---|---|
| Salesforce | salesforce |
Personal sign-in | Each person's Salesforce login |
| Salesforce Data 360 | data360 |
Personal sign-in | Each person's Salesforce login |
| Salesforce Marketing Cloud (Pilot) | sfmc |
Personal sign-in | Each person's Marketing Cloud login |
| SAP S/4HANA | s4hana |
Either | Your own system: each person's own SAP user, directly (Cloud Public Edition), through your SAP BTP login or through your SourceLace Agent. SAP's public demo sandbox: one key for everyone |
| SAP SuccessFactors | successfactors |
Shared account | The same: SAP's public demo sandbox only, for now |
| SAP ECC | ecc |
Personal sign-in | Each person's own SAP user, through your SourceLace Agent or your SAP BTP login |
| HubSpot | hubspot |
Personal sign-in | Each person's HubSpot login |
| Gmail and Google Calendar | google_workspace |
Personal sign-in | Each person's Google account |
| Outlook mail and calendar | microsoft365 |
Personal sign-in | Each person's Microsoft account |
| ServiceNow | servicenow |
Personal sign-in | Each person's ServiceNow login |
| Zendesk | zendesk |
Personal sign-in | Each person's Zendesk login |
| Jira Cloud | jira |
Personal sign-in | Each person's Atlassian account |
| Google Drive | google_drive |
Personal sign-in | Each person's Google account |
| SharePoint and OneDrive | microsoft_files |
Personal sign-in | Each person's Microsoft account |
| Amazon S3 | s3 |
Shared account | Your organization's AWS keys or role, set on the source |
| Snowflake | snowflake |
Personal sign-in | Each person's Snowflake login |
| Google BigQuery | bigquery |
Personal sign-in | Each person's Google account |
| Databricks | databricks |
Personal sign-in | Each person's Databricks login |
| Microsoft Dynamics 365 | dynamics365 |
Personal sign-in | Each person's Microsoft account |
| Microsoft Dynamics 365 Finance and Supply Chain | dynamics365_fo |
Personal sign-in | Each person's Microsoft account |
| Oracle NetSuite | netsuite |
Personal sign-in | Each person's NetSuite login and role |
| Gong | gong |
Shared account | Gong's sign-in gives the whole company's Gong data; Gong cannot limit it per person |
| Gainsight CS | gainsight |
Shared account | One access key for the whole organization; Gainsight cannot limit it per person, and the key can also change data in Gainsight (SourceLace only reads) |
| ChurnZero | churnzero |
Shared account | One API user and key; ChurnZero cannot limit it per person (a user whose permission group can only read makes it read-only) |
| Flexport | flexport |
Shared account | One API key for the whole organization; Flexport cannot limit it per person (SourceLace only reads) |
| Healthcare claims (Stedi) | claims |
Shared account | One Stedi API key for the whole organization; Stedi cannot limit it per person (SourceLace only reads) |
| SQL databases | database |
Personal sign-in | Each person's own database user name and password |
| MongoDB | mongodb |
Personal sign-in | Each person's own MongoDB user name and password |
| Oracle Fusion Cloud | oracle_fusion |
Personal sign-in | Each person's Oracle login |
| Workday | workday |
Personal sign-in | Each person's Workday login |
| Your own connector | custom |
Shared account | One secret links SourceLace and your connector. SourceLace tells the connector who is asking, so it applies per-person rules only if your developers built them |
| Google Sheets | google_sheets |
Personal sign-in | Each person's Google account |
| Slack | slack |
Personal sign-in | Each person's Slack account |
| Microsoft Teams | microsoft_teams |
Personal sign-in | Each person's Microsoft account |
| Lake tables | lake |
Shared account | Your organization's AWS keys or role, set on the source |
| Amazon Redshift | redshift |
Either | Personal by default (each person's own database user); shared when the admin names one shared database user |
| Amazon Athena | athena |
Shared account | Your organization's AWS role or keys, set on the source |
| SAP Datasphere | datasphere |
Personal sign-in | Each person's Datasphere login |
| Azure Data Lake and Blob Storage | azure_storage |
Personal sign-in | Each person's Microsoft account |
| Google Cloud Storage | gcs |
Personal sign-in | Each person's Google account |
| Microsoft Fabric, Azure Synapse | fabric |
Personal sign-in | Each person's Microsoft account |
| Trino and Starburst | trino |
Personal sign-in | Each person's own Trino login, by password or your identity provider |
| Health records (FHIR) | fhir |
Personal sign-in | Each clinician's own EHR login |
| Any REST API | rest |
Either | Personal with OAuth sign-in; shared with an API key, token, user name and password, or no sign-in |
| Any SOAP web service | soap |
Either | The same as REST |
| Outside MCP server | mcp |
Either | Personal with OAuth sign-in (the server's own); shared with a key or token, or no sign-in |
| Your own search index | search_index |
Either | Personal with each person's own sign-in where the service allows it; shared with an API key or login |
Who sets up what
| System | Your admin for that system | Your SourceLace admin | Each person |
|---|---|---|---|
| Salesforce, Data 360 | Either installs SourceLace's Salesforce app (a managed package) once, or creates their own app in their own org (no package), and decides who may use it | Adds the source with the org's login address (and, for their own app, its Consumer Key) | Signs in to Salesforce |
| Marketing Cloud (Pilot) | Creates a read-only installed package (Web App) in Marketing Cloud | Adds the source with the subdomain, Client Id and Client Secret | Signs in to Marketing Cloud |
| HubSpot | May need to approve SourceLace's HubSpot app | Adds the source | Signs in and approves the app |
| Google (Gmail, Calendar, Drive, Sheets, BigQuery) | May need to allow SourceLace's Google app; for BigQuery, grants IAM roles | Adds the source | Signs in with Google |
| Microsoft (Outlook, SharePoint and OneDrive, Dynamics 365, Dynamics 365 Finance and Supply Chain) | May need to grant admin consent to SourceLace's Microsoft app; for Dynamics, licenses and security roles | Adds the source | Signs in with Microsoft |
| ServiceNow, Zendesk | Registers an OAuth client in your instance | Adds the source with its Client ID | Signs in to ServiceNow or Zendesk |
| Jira Cloud | Nothing, unless your Atlassian organization restricts apps | Adds the source | Signs in and approves the site |
| Snowflake, Databricks | Creates an OAuth integration (Snowflake) or app connection (Databricks) | Adds the source with its client id | Signs in to Snowflake or Databricks |
| Microsoft Fabric, Azure Synapse | May need to grant admin consent for the Azure SQL permission (or registers your own Entra app); gives people access to the warehouse or database | Adds the source with the SQL endpoint and database | Signs in with Microsoft |
| NetSuite | Turns on OAuth 2.0 and REST web services; may need to install SourceLace's integration; gives roles the permissions | Adds the source with the account id | Signs in and picks a role |
| Gong | Nothing to register | Adds the source | Signs in to Gong; Gong only lets technical admins approve the app |
| Gainsight CS | A Super Admin makes an access key and tells you the Gainsight address | Adds the source with the address and the key | Clicks Connect (no sign-in page: the key is shared) |
| ChurnZero | ChurnZero switches its REST API on, and an admin makes a read-only user and API key | Adds the source with the API address, user name and key | Clicks Connect (no sign-in page: the user is shared) |
| Flexport | Someone with access to your Flexport account makes an API key (Your Business, Settings, API) | Adds the source with the key | Clicks Connect (no sign-in page: the key is shared) |
| Healthcare claims (Stedi) | An Admin or Developer of your Stedi account makes an API key (Developer settings, API keys) | Adds the source with the key | Clicks Connect (no sign-in page: the key is shared) |
| Databases | Your database administrator creates a read-only login per person and lets SourceLace's servers in | Adds the source with host and database | Signs in on SourceLace's form with their own database login |
| Amazon S3 | Creates read-only AWS access, arranged with SourceLace support | Adds the source with buckets and region | Clicks Connect (no sign-in page) |
| Oracle Fusion, Workday | Registers an OAuth client in your identity domain or Workday tenant | Adds the source with the client's details | Signs in to Oracle or Workday |
| Your own connector | Your developers build and run the connector | Adds the source with its address and shared secret | Clicks Connect (no sign-in page) |
| SAP ECC (on-premise) | Either your IT department runs the SourceLace Agent and your SAP Basis administrators trusts its CA (STRUST), maps certificates to users (CERTRULE) and activates the Gateway services; or, with no new outbound connection, your BTP administrators publishes the services through SAP BTP and Cloud Connector and registers SourceLace as an OAuth client | Agent: creates the agent's token, then adds the source with the agent's id. BTP: adds the source with the BTP address, login service, client and services | Agent: clicks Connect (no sign-in page). BTP: signs in once with their company's BTP login |
| Slack | May need to approve SourceLace's Slack app (Enterprise Grid: allow it per workspace) | Adds the source | Signs in to Slack |
| Microsoft Teams | Grants admin consent to SourceLace's Microsoft app (needed to read channel messages) | Adds the source | Signs in with Microsoft |
| SAP S/4HANA, SuccessFactors (SAP's public sandbox) | Nothing | Adds the source with auth set to sandbox |
Clicks Connect (no sign-in page); access is shared |
| Lake tables | Your AWS admin creates read-only access to the tables' folder (and Glue, if used) | Adds the source with the location, tables and direct_reads on |
Clicks Connect (no sign-in page) |
| Amazon Redshift | Creates an IAM role (or keys) that may get database credentials, and a database user per person named by their email | Adds the source with the cluster or workgroup and database | Clicks Connect (no sign-in page); queries run as their own database user |
| Amazon Athena | Creates a workgroup with a per-query data limit and an IAM role (or keys) that may query it | Adds the source with the workgroup | Clicks Connect (no sign-in page); access is shared |
| SAP Datasphere | Adds an OAuth client with the purpose Interactive Usage on App Integration | Adds the source with the tenant address, Authorization URL and the client's id and secret | Signs in to Datasphere |
| Azure Data Lake and Blob Storage | Gives people Storage Blob Data Reader (and Data Lake ACLs); may need to grant consent for the Azure Storage permission | Adds the source with the storage account and containers | Signs in with Microsoft |
| Google Cloud Storage | Gives people Storage Object Viewer on the buckets | Adds the source with the buckets | Signs in with Google |
| Trino and Starburst | Nothing for password sign-in; for OAuth, registers an OAuth client with the identity provider the cluster trusts (or in Galaxy) | Adds the source with the cluster address (and the OAuth client) | Signs in with their own Trino login, or on the identity provider's page |
| Health records (Epic, Oracle Health, MEDITECH) | The hospital's EHR team activates SourceLace's own app in their Epic or Oracle Health system (MEDITECH and others: registers an app) | Adds the source with the FHIR base URL (a client id only for MEDITECH, other EHRs or an app of your own) | Signs in to the EHR |
| Any REST or SOAP system | Registers an OAuth client for SourceLace, or creates a least-access API key or service account | Adds the source with the API's description (OpenAPI document, WSDL or endpoints) and sign-in | OAuth: signs in with their own account. Shared key: clicks Connect (shared access) |
| Outside MCP server | Usually nothing: SourceLace registers itself with the server's sign-in. Otherwise registers an OAuth client, or creates a least-access key | Adds the source with the server's address, then chooses the allowed tools with Test connection | OAuth: signs in with their own account on the vendor's page. Shared key: clicks Connect (shared access) |
How queries stay read-only
Every query is checked by SourceLace before anything is sent to your system: it must be in the language that source accepts, and anything that could change data is refused (for example INSERT, UPDATE, DELETE, MERGE, CREATE, DROP in SQL, more than one statement, or $out and $merge in MongoDB). Each setup page lists that source's checks. Where the system offers it, SourceLace also asks the system itself for read-only access: a read-only transaction in PostgreSQL and MySQL, read-only OAuth scopes, a byte cap in BigQuery.
An ordinary result holds up to 2,000 rows, of which 50 are shown to the AI at a time; a larger answer, up to 250,000 rows, is kept whole in SourceLace's short-lived encrypted engine. Results are held for at most 30 minutes, so they can be joined, charted or made into a document, and are never written to a database (see How long things are kept).
When something goes wrong
These messages can come from any source. Each setup page also lists the messages specific to that system.
| What you see | What it means and what to do |
|---|---|
| "You have not connected source yet. Call connect_source to sign in with your own account." | Connect the source: ask your AI to connect it, or click Connect on My connections. |
| "Your sign-in to source has expired. Call connect_source to sign in again." | The system ended your sign-in (for example its refresh token expired or was revoked). Connect again. |
| "source did not accept your sign-in (...). Call connect_source to sign in again." | The system refused a fresh token too, often because your account or its permissions changed. Connect again; if it keeps happening, check your access in that system. |
| "This sign-in link has expired or was already used. Ask for a new one." | Connect links work once, for 10 minutes. Ask for a new link. |
| "Sign-in was not completed: ..." | The system's sign-in page reported a problem. The rest of the message is the system's own reason and, in brackets, its error code, such as "(error OAUTH_APPROVAL_ERROR_GENERIC)": look the code up in that system's chapter. Common reasons are a redirect URL that does not match, or consent that was refused. |
| "There is no source called '...'. Call list_sources to see them." | The source id is mistyped, or the source was removed. |
| "Your groups in SourceLace do not give you access to ..." | Access by group is on and none of your groups gives you this. Ask a SourceLace admin. |
| "Writes to object are turned off for source. An admin can enable them per source and object." | A SourceLace admin must turn on Allow changes for that source and list the object. |
| "source does not accept changes through SourceLace." | That kind of source is read-only in SourceLace. |
| "The kind connector is not set up on SourceLace yet. Contact SourceLace support ..." | SourceLace's app for that system is not ready for your organization yet. Contact support@sourcelace.com. |
| "The kind connector is not available yet." | That kind of source is not built yet. |
| "source accepts ..., not ..." | The query was written in the wrong language for that source. The AI usually corrects this itself. |
| "source could not be reached." or "... did not answer in time. Try again shortly." | The system was down, slow, or blocked SourceLace's connection. Try again; for databases, check the firewall (see Databases). |
| "Result ... has expired or does not exist. Run the query again." | Results last up to 30 minutes, and sooner when SourceLace is holding many results at once. Run the query again. |
| "Your organization is holding its share of large results ..." or "... using its share of this server's space for large results" | Your organization already holds as many large results as it fairly can at the moment, so others can work too. Try again once older results expire or you close old chats, or narrow the question. |
| "This server is short of space for large results right now.", "This server ran out of disk space while it was writing a large result." or "SourceLace is holding as many large results as it can right now." | SourceLace is busy with large results. Try again in a few minutes, or narrow the question. |
| "Change ... has expired, was already applied, or does not exist. Propose it again." | A change preview lasts 10 minutes and applies once. Ask for a new preview. |
| "SourceLace hit an unexpected problem ... Try again; if it keeps happening, tell your admin or SourceLace support." | Something SourceLace did not expect. It is logged for SourceLace support (without your data); write to support if it repeats. |