Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.frontic.com/llms.txt

Use this file to discover all available pages before exploring further.

n8n
There’s no dedicated n8n connector — instead, n8n becomes a Frontic source by pushing records into a Custom integration via the Ingest API. Use this when n8n is already orchestrating data between systems and you want to push enriched records to Frontic and no other connector is available.
Auth
Ingest API token
Update method
Ingest API (push from n8n)
Resources
Anything you push

​
When to reach for n8n

Use this pattern when:
  • You already run n8n to orchestrate data flow between systems and want Frontic to receive the enriched output.
  • The source you want to ingest from doesn’t have a first-party Frontic connector and you’d rather configure n8n than write code.
  • You need a transformation step (deduplication, enrichment from another API, scheduled aggregation) before records get pushed to Frontic.
If your source is a system Frontic already connects to (Shopware, Shopify, Akeneo, …), use that connector directly — there’s no advantage to routing through n8n.

​
How it works

Set up a Custom integration in Frontic

Create a Custom integration and add a Data Feed for the resource type you’ll push. Note the feed’s Ingest API endpoint and create an Ingest API token — see Ingest API → Auth.

Build the n8n workflow

In n8n, build a workflow that produces records in the Custom integration’s payload shape. Trigger it on a schedule, on webhook, or from any other n8n trigger node.

Add an HTTP Request node

Use the Frontic Ingest API node in n8n to POST to the Frontic Ingest API endpoint. Set:
  • Ingest Operation: Create or Update for adding data, Delete for removing records
  • Frontic Ingest API Credentials: Choose your configured Frontic credentials form n8n
  • Payload: For adding data, use the record JSON (or an array of records for bulk upsert). For removing records, pass an object with the record’s ID (or an array of ID objects for bulk removal).

Test and deploy

Run the workflow once to confirm records land in your Frontic feed, then activate it. From here on, every n8n run pushes its output into Frontic.

​
What the data looks like

You define the record structure in n8n. Match the Custom integration’s record structure conventions — the connector recognises @channel, @translation, and @currency annotations for context-specific values.

​
Good to know

  • You own the schema. No normalization happens on the connector side — what you push is what’s stored on the feed (reshaping into your storage schema is the Data Sync’s job).
  • No webhooks back to n8n. This is a one-way push from n8n into Frontic. If you need Frontic to notify n8n of stack changes, use a separate webhook source on the n8n side.
  • Quota counting. Every push from n8n counts against your API Updates quota the same as any other Ingest API call. Schedule deliberately.

Custom Integration

The Frontic-side configuration n8n posts to.

Ingest API

The HTTP endpoints, payload shape, and auth model.