n8n

The Comers n8n node lets an n8n workflow receive supported Comers Events without manually creating and maintaining webhook subscriptions.

The package is published as:

@comers/n8n-nodes-comers

It provides a Comers Trigger node and a Comers API credential.

flowchart TD
    C[Comers Event] --> T[Comers Trigger]
    T --> N[n8n workflow]
    N --> A[Another n8n node]
    A --> X[External application]

Install the community node

In an n8n installation that allows community nodes:

1. open Settings → Community nodes,
2. choose to install a community node,
3. enter @comers/n8n-nodes-comers.

Availability of community nodes can depend on how your n8n environment is hosted and administered.

Create the Comers credential

The node connects to Comers through a machine integration.

Create the integration in Comers with the event-subscription access required by the n8n node. Comers provides the client credentials used by the connection.

Then create a Comers API credential in n8n and provide:

• the public URL of your Comers installation,
• the client ID,
• the client secret.

Treat the client secret as sensitive. Store it only in the n8n credential and the designated Comers integration flow.

Add Comers Trigger

Add Comers Trigger to the workflow and select the Comers API credential.

The node loads the supported event choices from the Comers event catalogue rather than relying on a permanently hard-coded list inside the node package.

This means new supported event types can become selectable without requiring the node package to contain a static copy of the entire Comers event catalogue.

Choose the events

Select the events that should start the workflow.

Choose only the business events the workflow actually needs. Keeping subscriptions focused makes the workflow easier to understand and avoids unnecessary executions.

The exact event list depends on the catalogue exposed by your Comers installation.

Publish the workflow

Publishing the n8n workflow creates or updates the workflow’s production Comers event subscription.

Unpublishing or deleting the workflow retires the subscription managed by that node.

This lifecycle is intentional: you do not need to manually copy a production webhook URL into Comers and then remember to remove it when the workflow is no longer active.

flowchart TD
    D[Design workflow] --> E[Select Comers events]
    E --> P[Publish workflow]
    P --> S[Subscription active in Comers]
    S --> R[Verified event starts workflow]
    R --> U{Workflow unpublished or deleted?}
    U -->|No| S
    U -->|Yes| A[Subscription archived]

Test events

When you use n8n’s test-listening mode, the node can create a separate temporary subscription for the editor’s test webhook.

The test subscription is separate from the production subscription so testing does not replace or take ownership of the live workflow subscription.

Verified deliveries

The Comers Trigger verifies supported signed deliveries before the workflow is executed.

This keeps signature verification inside the connector instead of requiring every workflow author to rebuild verification logic with generic n8n nodes.

A successful trigger means n8n accepted a verified Comers delivery. It does not guarantee that the rest of the workflow will succeed.

Build idempotent workflows

Comers event delivery can be retried or replayed.

The same business event can therefore reach the workflow more than once. When duplicate processing would be harmful, deduplicate using the stable event identifier delivered in the event envelope.

Do not use the delivery attempt number as the identity of the business event.

What the workflow receives

The trigger exposes the signed Comers event envelope together with delivery information.

The event contains the business event identity and context supplied by Comers. Fields can evolve together with supported event versions, so downstream workflow logic should use the fields required by its specific event contract rather than assume all events have the same payload.

When to use n8n

n8n is a good fit when you want to:

• connect a Comers event with an application already available in n8n,
• transform or enrich event data,
• route different events into different processes,
• add customer-specific automation without building a native Comers connector,
• prototype an integration workflow before deciding whether it needs a dedicated service.

For the underlying event model, see Events & webhooks.