Pipelines
A pipeline listens for a specific Shopify webhook event and forwards it to a destination URL. You can optionally reshape the payload, add authentication, and control delivery rate.
Pipelines List
The Pipelines page shows all configured pipelines in a table:
| Column | Description |
|---|---|
| Pipeline Name | Your chosen pipeline name |
| Shopify Topic | The webhook event type (e.g. products/update) |
| Status | Active (green) or Disabled (grey) |
| Traffic (24H) | Sparkline of requests over the past 24 hours |
| Errors (24H) | Sparkline of delivery failures over the past 24 hours |
Click Edit on any row to open the pipeline editor.
The Add Pipeline button appears when your plan allows more pipelines. If you have reached your plan's limit, an Upgrade Plan button is shown instead.
Creating or Editing a Pipeline
The pipeline editor is divided into four sections.
1. Route Configuration
| Field | Description |
|---|---|
| Pipeline Enabled | Toggle off to pause delivery without deleting the pipeline |
| Pipeline Name | A human-readable label shown in the list and in failure reports |
| Shopify Webhook Event Trigger | The event that activates this pipeline (e.g. orders/create) |
| Destination URL | The HTTPS endpoint Shop Vector should forward the payload to |
TIP
There's nothing to set up in Shopify's Notifications settings. When you enable a pipeline, Shop Vector automatically registers the Shopify webhook for the selected topic (and removes it when no pipeline needs it).
2. Payload Remapping
Enable Remap Fields to transform the Shopify payload before it is delivered. When enabled, a visual node editor appears.
Working with the remapping canvas
- Add Input Node — select a Shopify source property from the dropdown and click the button to add it as a node on the left side of the canvas.
- Add Output Node — enter the destination field path (e.g.
items[].id) and click the button to add it as a node on the right side. - Add Templated Field (Scale and Enterprise plans) — enter the destination field path, then click the button to add a templated field. See Templated fields below.
- Connect nodes — drag from a source node to a destination node to map one field to the other.
- Rename or delete a node — right-click any node to open a context menu.
- Auto Arrange Canvas — click this button to tidy the layout automatically.
- You can pan the canvas by dragging the background and zoom with the scroll wheel.
If remapping is disabled, the full original Shopify payload is forwarded unchanged.
Templated fields
Available on the Scale and Enterprise plans. A templated field produces a single output field whose value is either static text or a template that combines several source fields, rather than a straight copy of one input.
Unlike a regular output node, a templated field is not wired to input nodes. Instead, you reference source fields directly inside its value using ${field} placeholders.
To create one:
- Enter the output field path (e.g.
message) in the output path box and click Add Templated Field. - Click inside the field's value box on the canvas.
- Type static text, and insert source fields where you need them. With the value box focused, pick a source property from the dropdown and click the Insert button to drop in a
${field}placeholder at the cursor. You can also type placeholders by hand. - Right-click the node to rename its output field or delete it.
Changing the event type reloads the available source fields for payload mapping.
Example
With a field name message and source fields customer.first_name and order.number, a value of:
Hi ${customer.first_name}, thanks for order #${order.number}produces:
{
"message": "Hi Jane, thanks for order #1001"
}Any placeholder that does not match a known source field, or an empty output field name, is flagged as invalid and blocks saving until corrected.
Arrays are not supported
Templated fields work with scalar values only. Neither the output field path nor any ${field} placeholder may use array ([]) notation. Deeper scalar paths such as customer.address.city are fine.
3. Authentication & Signing
These options control how Shop Vector authenticates outbound requests to your destination.
HMAC Signing
Available on all plans. When enabled, Shop Vector adds a signature header to every request so your endpoint can verify the payload has not been tampered with and originated from Shop Vector.
| Field | Description |
|---|---|
| Header Name | The HTTP header Shop Vector will add (e.g. X-HMAC-Signature) |
| Secret Key | The shared secret used to compute the signature |
| Digest Algorithm | Base64 or HEX encoding for the signature value |
OAuth 2.0
Available on the Scale and Enterprise plans. When enabled, Shop Vector fetches a bearer token from an OAuth2 server to attach to each delivery.
| Field | Description |
|---|---|
| Client ID | Your OAuth2 client identifier |
| Client Secret | Your OAuth2 client secret |
| Token Endpoint URL | The URL Shop Vector calls to obtain a token |
| Scopes | Comma-separated scopes, each in quotes (e.g. "read", "write") |
Mutual TLS (mTLS)
Available on the Enterprise plan. When enabled, Shop Vector presents a client certificate to your destination on every request, allowing it to verify that the connection originates from Shop Vector.
| Field | Description |
|---|---|
| Client Certificate | The PEM-encoded certificate Shop Vector presents to your server |
| Client Private Key | The PEM-encoded private key corresponding to the client certificate. Required. |
| Server CA Certificate | (Optional) The PEM-encoded CA that signed your destination's server certificate. Provide this when your server uses a private or self-signed CA. Leave blank to verify against public system CAs. |
| Skip server certificate verification | Disables server certificate verification entirely. Insecure — for testing only. |
4. Delivery Constraints
Rate Limiting
Available on the Scale and Enterprise plans. Enable Rate Limiting and set a Max Requests per Second to prevent Shop Vector from overwhelming your destination.
Custom HTTP Headers
Add custom headers to every forwarded request. Click Add to insert a new key/value row, and the delete icon to remove one. Useful for API keys or routing tokens your destination requires.
Saving and Deleting
- Save — persists all changes. The pipeline becomes active within the next few seconds if it is enabled.
- Cancel — discards changes and returns to the pipelines list.
- Delete Pipeline — permanently removes the pipeline. A confirmation dialog is shown before deletion. This action cannot be undone.