FWO Get Content Fields

Consume FWO API to fetch content fields using multiple Field IDs and optional Card ID
Join our community

Overview

This node, named "FWO Get Content Fields," is designed to fetch content field data from an external API (referred to as FWO API) by querying multiple Field IDs. Optionally, it can refine the query using a Card ID to filter results more specifically. It is useful in scenarios where you need to retrieve the latest content values associated with specific fields, potentially scoped to a particular card or context.

Practical examples include:

  • Retrieving the most recent content for a set of form fields identified by their IDs.
  • Filtering content data related to a specific card or entity by providing its Card ID.
  • Integrating with systems that store field-based content and require up-to-date information for reporting or processing.

Properties

Name Meaning
Field IDs A collection of one or more Field IDs (strings). Each ID represents a unique field to query.
Card ID (Optional) An optional string representing a Card ID to narrow down the query results to a specific card.

Output

The node outputs an array of JSON objects, each corresponding to a requested Field ID (and optionally filtered by Card ID). Each output item contains:

  • fieldId: The queried Field ID as a string.
  • cardId: The Card ID used for filtering, or null if none was provided.
  • response: The raw response data from the API, which includes:
    • fieldsValues: An array containing the latest content value(s) for the field, including:
      • id: The ID of the field value record.
      • card: Object with name and id of the card associated.
      • field: Object with id and name of the field.
      • content: The actual content stored in the field.

If the node encounters errors and is configured to continue on failure, it outputs an object with an error property describing the issue.

Dependencies

  • Requires an API key credential to authenticate with the external FWO API.
  • The node makes HTTP POST requests to the API endpoint specified in the credentials.
  • The API expects GraphQL queries to fetch the field content data.

Troubleshooting

  • No credentials returned!: This error occurs if the required API authentication credentials are missing or invalid. Ensure that the API key credential is properly configured in n8n.
  • API request failures: Network issues, incorrect Field IDs, or invalid Card IDs may cause errors. Verify that the IDs are correct and that the API endpoint is reachable.
  • Empty responses: If no content is returned, check whether the Field IDs exist and if the optional Card ID is valid.
  • To handle errors gracefully, enable the "Continue On Fail" option in the node settings to prevent workflow interruption.

Links and References

Discussion