FlexCards are declarative UI components that display contextual data; each FlexCard is configured with one or more data sources that are fetched when the card renders.
In the FlexCard editor, add a data source of type 'DataRaptor', 'Integration Procedure', or 'SOQL' (available source types may vary); configure the relevant bundle name or IP Type/SubType.
For a DataRaptor Extract data source, map input context keys (from the FlexCard's context record) to the DataRaptor's input variables to filter results to the relevant record.
For an Integration Procedure data source, define the input parameters the IP requires and map them from the FlexCard context.
After configuring the data source, map the output fields to FlexCard element bindings using dot-notation expressions (e.g., {records.0.Name}).
Activate the FlexCard and deploy it to a Lightning page or OmniScript to verify the data source fetches the expected data.
Known gotchas
FlexCard data sources are fetched on component load; if the data source integration procedure is slow or calls external systems, this directly impacts page load time for end users.
The available data source types in the FlexCard editor depend on your OmniStudio version and namespace; verify supported types in your environment.
Data source output bindings are case-sensitive; a mismatch between the output key from the DataRaptor and the binding expression in the FlexCard element results in empty display values.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp