n8n Workflow Trigger
Trigger self-hosted or cloud n8n workflows from product events with signed payloads.
What it adds
An outbound trigger to user-supplied n8n webhook URLs, with shared-secret signing, versioned payloads, and a bounded wait for responding workflows.
What your agent is told to do
5
What your agent is told to do
5-
1
Treat every destination as untrusted because self-hosted n8n means the user picks the host. Resolve the hostname before each connection, reject private, loopback, link-local, and metadata addresses, and re-check on redirect rather than only when the URL is saved.
-
2
Offer an optional shared secret per destination. When it is set, sign the request body with it and include a timestamp in the signed material so the workflow can verify origin and reject replays.
-
3
Version the payload for each event type and include the version in the body. Add fields without removing old ones, and treat any removal or rename as a new version so live workflows keep parsing what they were built against.
-
4
Bound the wait for workflows that respond synchronously. Apply a short connect and read timeout, treat anything past it as an unacknowledged delivery, and never hold a user-facing request or a job worker open waiting on someone else's server.
-
5
Reuse the shared outbound delivery pipeline from the Zapier Trigger Webhook brief for queueing, retry, logging, and auto-disable. This brief owns only the SSRF checks, the shared-secret signing option, and the synchronous-response handling.
Edge cases it handles
8
Edge cases it handles
8- A self-hosted URL is the most direct route to server-side request forgery this app will ever offer. Validate the scheme and resolved address on every attempt, not once at save time, because DNS can be repointed at an internal host afterwards.
- Not every user will configure a secret, and an unsigned payload cannot be trusted by the receiver. Support an optional shared secret, make its absence visible in the settings screen as a reduced-assurance state, and allow rotating it without recreating the integration.
- A workflow written against last quarter's payload will break on an unannounced field change. Keep schemas versioned, publish the current version in the body, and keep at least one prior version working through a stated deprecation window.
- A workflow that responds synchronously can hang for as long as its slowest node. Enforce a timeout, release the worker, and record the delivery as sent-but-unacknowledged rather than blocking the app indefinitely.
- Retrying a delivery whose workflow already ran can duplicate side effects such as sending a message or charging a customer. Retry only where the delivery was not acknowledged, carry a stable delivery identifier so the workflow can deduplicate, and do not retry a workflow that returned a definitive rejection.
- A self-hosted instance behind a home connection will be intermittently unreachable. Back off with jitter, cap the retry window, and disable the destination after a sustained run of failures with a clear message to the owner.
- A user-supplied host may present an invalid or self-signed certificate. Require a valid chain by default, and if an override is offered at all, scope it to the single destination and make the reduced security explicit.
- When n8n is unavailable, the app must continue working normally. Show the integration as degraded with the last successful delivery time, and never surface the third party's failure as an error on the user's own action.
Definition of done
8
Definition of done
8- Destination hosts are resolved and validated on every attempt, and internal-network targets are refused.
- An optional shared secret signs the payload with a timestamp, and can be rotated in place.
- Payload schemas are versioned, the version travels in the body, and prior versions keep working through a deprecation window.
- Synchronous workflows are bounded by a timeout that never blocks a user request or holds a worker open.
- Only unacknowledged deliveries are retried, and each carries a stable delivery identifier.
- An unreachable n8n instance leaves the app fully usable and the integration visibly degraded.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Contentful Entry Sync
Contentful Entry Sync
Create and update Contentful entries against the connected space, environment, and locale.
What it does
A sync that writes app records into Contentful entries using the connected space's content model and locale configuration.
How it works
- 1 Have the operator select the space, the environment, and the default locale during connection, and store all three, because writing production content into a sandbox environment is an easy and expensive mistake.
- 2 Fetch the content model at connection time and again before each sync run, map app fields to entry fields by their stable identifiers, and validate the value type against the model before attempting the write.
- 3 Write every localized field under an explicit locale rather than relying on whatever the space treats as default, and state clearly which locales the app owns and which it leaves to editors.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/contentful-entry-sync
Typesense Index Sync
Typesense Index Sync
Keep a search index in step with your records so results stay current and correctly scoped.
What it does
A one-way sync from the app's records into a Typesense collection, with server-enforced tenant filtering and a rebuild path.
How it works
- 1 Identify every model users search today and declare the indexed shape explicitly: the fields people type into, the fields they filter and sort on, and nothing more. Treat a missing or newly added field as absent rather than letting the document fail validation.
- 2 Reuse the app's existing background-job system to push creates, updates, and deletes. Do not index inside the request cycle; a slow or unreachable search service must never make a save fail or hang.
- 3 Build the tenant, workspace, and permission filter on the server at query time and attach it to every search. Do not accept a filter, collection name, or scope value from a client-supplied parameter, because anything the browser can set the browser can change.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/typesense-index-sync
Mapbox Geocoding
Mapbox Geocoding
Convert typed locations into coordinates and structured addresses the app can use.
What it does
Forward and reverse geocoding with confirmed matches, controlled result bias, and coordinate precision rules.
How it works
- 1 Separate the two directions explicitly: text to coordinates for entry and search, coordinates to address for a dropped pin or a device location. They take different inputs, carry different confidence, and fail differently.
- 2 Present ambiguous matches as a list the user confirms. Silently taking the first result is how a record ends up in the wrong country with nobody noticing for months.
- 3 Bias results toward a location only when the app genuinely knows one, such as a workspace address or the map viewport the user is already looking at.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/mapbox-geocoding
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.