Connecting source systems
MetaFabric connects to the systems you already run and discovers their objects and fields. It can then read the data where it lives, or bring a copy in.
Supported systems#
| System | How it signs in |
|---|---|
| Salesforce | OAuth client credentials or JWT bearer |
| ServiceNow | Username and password, or OAuth 2.0 |
| Jira Cloud | Account email and API token |
| Supabase and RingCX | Project secret key |
| NetSuite and Workday | Sandbox data for now |
| Custom connector | Set by the connector |
| Excel and CSV | File upload |
For availability and limits, see Capabilities at a glance.
MetaFabric connects using the permissions of the account you provide. We recommend a dedicated integration account with only the access it needs. Credentials are checked before they are saved, and stay hidden afterward.
Read live or bring data in#
Each mapping uses one of two modes. The console names are shown in brackets.
Records stay in the source. MetaFabric reads them when someone asks.
Choose it when: the source remains your main system and you want current data without keeping a copy.
Records are copied into MetaFabric and combined with other sources, with lineage, checks and certification.
Choose it when: you need one trusted view across systems, or MetaFabric will become the main system.
Supabase sources support Bring in and unify only.
Changes to Salesforce. With Read live, records you create, edit or delete in MetaFabric are sent to Salesforce first. They are kept only if Salesforce accepts them.
Switching modes. Records already copied into MetaFabric are not deleted when a mapping changes to Read live. They stay until someone removes them.
Keeping data current#
Refreshes imported data automatically at the interval you set on the Knowledge fabric page.
Refreshes the data straight away, whenever you need it.
Your system sends new or updated records straight to MetaFabric's API.
Read live sources copy no records when they sync. They are always current. The methods available depend on the connector.
Custom connectors#
For any other system, a developer builds a connector with the MetaFabric connector kit, and an admin uploads it under Mappings → Custom connectors. Its settings are stored encrypted. A connector declares what it can do: discover, read and count are standard, and a connector that also declares write support can send changes back to its source.
Setup guides#
Short steps for each system. Most take 10 to 20 minutes with an admin of that system.