CustomJE icon

CustomJE

Custom operations

Overview

This node performs a data combination operation by querying a Supabase table and merging specified fields from the retrieved records into a single combined string per record. It is useful when you want to aggregate multiple fields of database entries into a concise, formatted output for further processing or reporting.

Typical use cases include:

  • Combining customer information fields (e.g., name, phone, status) into a single string for display or export.
  • Aggregating multiple attributes of database rows with a custom separator for easy parsing downstream.
  • Filtering and limiting data fetched from Supabase before combining fields.

For example, you might combine the fields name, phone, and email separated by a dash (-) for each customer in a "customers" table, optionally filtering only active customers.

Properties

Name Meaning
API Key Your CustomJE API key used for authenticating requests to the CustomJE service.
Supabase URL The URL of your Supabase project (e.g., https://your-project.supabase.co).
Supabase Anon Key Your Supabase anonymous API key for accessing the Supabase database.
Table Name The name of the Supabase table to query (e.g., customers).
Combine Data Fields List of fields from the table to combine, separated by the separator symbol (e.g., name - phone - email).
Separator Symbol Symbol used to separate combined fields in the output string (default is -).
Filter Condition Optional filter condition for the query, e.g., status=eq.active to filter active records.
Limit Maximum number of results to return from the query (minimum 1, default 50).

Output

The node outputs an array of JSON objects representing the combined data results returned from the CustomJE API after querying Supabase. Each item typically contains the combined string of the specified fields for one record.

The exact structure depends on the external API response but generally includes the combined field values as a single string per record.

No binary data output is produced by this operation.

Dependencies

  • Requires access to the CustomJE API via an API key.
  • Requires a valid Supabase project URL and anonymous API key to query the Supabase database.
  • The node makes HTTP POST requests to https://api.customje.com/combine-data.php to perform the combination logic externally.
  • Proper configuration of these credentials and URLs within n8n is necessary for successful execution.

Troubleshooting

  • Invalid API keys or URLs: Ensure that the CustomJE API key, Supabase URL, and Supabase anon key are correct and have appropriate permissions.
  • Filter syntax errors: The filter condition must follow the expected format (e.g., field=eq.value). Incorrect filters may cause no data to be returned or errors.
  • Empty or incorrect table name: Verify the table name exists in your Supabase project and is spelled correctly.
  • Exceeded limits: If the limit is set too high, the API or Supabase may throttle or reject the request.
  • Network issues: Connectivity problems between n8n and the external APIs will cause failures.
  • API errors: The node throws errors if the operation or resource is unknown or not implemented; ensure the correct Resource ("Data Processing") and Operation ("Combine Data via Supabase") are selected.

Links and References

Discussion