Supergraph
The Supergraph Task
is used to extract data from Fenergo using our Supergraph API. It runs a pre-configured query that allows users to select what datasets to include.Configuration
| Configuration | Description |
|---|---|
| Query By | Available parameters to drive the query: JourneyId - automatically mapped to {{Execution.Request, $.journeyId}} for Journey Triggered Flows but this can be adapted for other trigger types EntityId - for querying by EntityId |
| Query By Value | Value to use for the selected Query By option. Must resolve to a valid GUID. |
| Entity | Includes the Verified record for the Journey's Lead Entity |
| Entity Draft | Includes the Draft record for the Journey's Lead Entity. Includes ProposedChanges which highlights the changes between the Verified and Draft records |
| Related Parties | Includes Associations and Verified/Draft Entity Data for Related Parties records |
| Product Drafts | Includes Product Drafts edited within current Journey |
| Product Associations | Includes Associated Products (verified) |
| Stages | Includes Journey Schema details |
Node Retrieval Limit
The Related Parties, Product Drafts, and Product Associations collections are retrieved using pagination. A maximum of 500 nodes can be returned per collection. If a collection exceeds this limit, only the first 500 nodes will be included in the response.
If you expect more than 500 Related Parties to be in scope, consider using the Association Query APIs directly via the HTTP Invoker task instead.
Task Output
Supergraph produces the following Task Output that can be used as Variable Input in your subsequent tasks.
| Output Variables | DataType | Description |
|---|---|---|
| ResponseBody | Json | Raw supergraph query API response. Optionally includes Stages, Entity, EntityDraft, and RelatedParties based on configuration. |
| FormattedResponse | Json | Parsed Supergraph Response to quickly access data frequently needed by Integrations... Entities is a distinct list of each entity in the query response. Draft records are prioritized and identified via the IsDraft attribute. Products will be available in a future release |