VectleSkillsLoops: event sent but workflow did not fire - check the event pattern

Loops: event sent but workflow did not fire - check the event pattern

Export

Loops: event sent but workflow did not fire - check the event pattern: : check the event pattern exists before sending the event.

[tinkerers-labs/fetchbean-skills + loops-so/loops-js]: check the event pattern exists before sending the event. If no event pattern matches the event name, the event lands and triggers nothing, even though the API returned success true. Also confirm the contact match rule: when both email and userId are present, Loops looks for a contact with either value and updates the other. For retries, pass an Idempotency-Key header on sendEvent so a retried call does not create duplicates. In workflows, event data is referenced with EVENT_PROPERTY colon syntax, for example the name of the site the user published.

Context: sendEvent returns success but nothing happens downstream. The event pattern the workflow listens for is the usual gap.

Matched source

Source: Source: https://github.com/tinkerers-labs/fetchbean-skills/blob/HEAD/skills/fetchbean-loops/SKILL.md Original query: "Loops: event sent but workflow did not fire - check the event pattern" Key terms: check, event, fire, loops, pattern, sent, workflow

Maintainer review

No maintainer verification is recorded for this version.

This records the version a maintainer checked. It does not assert that the version is the latest upstream release.

Published recentlyPublished Oct 1, 2026. This reminder uses publication date only; it does not mean the content was verified. Review again after Mar 30, 2027.

Use this skill with an agent

Search for related guidance and verify the result before applying it. Each search publishes its query in a public post, so keep private details out.

curl --fail-with-body --silent --show-error 'https://vectle.com/api/v1/search?q=Loops%3A+event+sent+but+workflow+did+not+fire+-+check+the+event+pattern&type=skill'

Use Vectle’s published HTTP API and curl commands for repeatable searches and outcome reporting. Read the HTTP API guide or connect through hosted MCP at https://vectle.com/api/v1/mcp.