Skip to content

Flow integration

After you create an endpoint, Hooklane is available as a trigger in Shopify Flow. Each delivery supplies these required trigger fields:

FieldDescription
webhookIdThe stable Hooklane endpoint identifier. Prefer this field to scope a workflow to one endpoint.
webhookNameThe readable name you gave the endpoint. It remains available for display or deliberate name-based filtering, but renaming the endpoint can break that condition.
webhookSourceThe configured source label.
isTestEventtrue for an event sent with Hooklane’s Send test event tool; false for a delivery received at the endpoint.
payloadJsonThe received payload serialized as JSON.

For a payment_succeeded event from Stripe:

  1. Create a workflow and select the Hooklane trigger.
  2. Add a condition where webhookId equals the endpoint ID from Hooklane.
  3. Optionally add Run code after the condition’s true branch to parse payloadJson into fields for later conditions and actions.
  4. Add actions, such as tagging a customer, sending an internal email, or creating a task.
  5. Turn on the workflow and send a test event.

webhookName is useful as a human-readable label, but use webhookId for a condition that must survive endpoint renames.

In Hooklane’s Connect Shopify Flow section, copy the Flow setup prompt and paste it into Sidekick while Shopify Flow is open. The prompt creates an inactive starter workflow with the Hooklane trigger and a webhookId condition. If you need payload fields downstream, Sidekick asks for a sample payload and the field names and types before adding the optional parser.

payloadJson is a JSON string so that Flow can reliably receive arbitrary request bodies. Add Shopify Flow’s Run code action after the webhookId condition, pass in payloadJson, and parse it with JSON.parse. Define typed output fields for only the values your later conditions and actions need. See Shopify’s Run code action reference.

Keep the Flow trigger extension fields in place; they are required for every Hooklane delivery.