Use NudgeForMe in n8n

The simplest n8n integration uses the HTTP Request node and a developer API key. You do not need a dedicated n8n Nudge node.

Setup

1. Create a read-only key in NudgeForMe → Settings → Developer API.
2. In n8n, create an HTTP Request node.
3. Set Method to GET.
4. Set URL to https://app.nudgeforme.com/api/v1/opportunities (or https://europe.nudgeforme.com/api/v1/opportunities for EU).
5. Under Authentication, configure a Bearer Auth credential with your Nudge API key.
6. Optionally set query parameters workspaceId and limit.
7. Execute the node. The response is JSON.

Avoid entering the key directly into a node body or URL.

Sample workflow: weekly opportunity digest

Schedule Trigger → HTTP Request: GET /opportunities → Filter → Email/Slack summary

Keep this workflow read-only and avoid distributing recipients or email subjects outside approved tools.

Sample workflow: CRM-based follow-up drafting

CRM trigger → find an already-sent thread → check existing watch status → watch the thread (if needed) → create a draft → notify a reviewer

Use a dedicated key with nudge.conversations.write and nudge.drafts.write only for this workflow. Provide a stable Idempotency-Key header on every POST and use mailbox Draft mode.

POST node example

URL: https://app.nudgeforme.com/api/v1/drafts
Method: POST
Authentication: Bearer Auth
Headers: Content-Type: application/json, Idempotency-Key: n8n-draft-unique-123

JSON body:

{"threadId":"EXISTING_WATCHED_THREAD_ID","research":false}

This operation creates a draft and never sends email.

Rate limiting and retries

Developer keys have a limit of 60 requests per minute per key. Use n8n's batching/wait controls, back off on 429, and avoid blindly retrying POSTs with new idempotency keys after timeouts.

OAuth alternative

Integrations built for multiple Nudge users can use Nudge's OAuth authorization-code/PKCE flow. Dynamic OAuth client registration may be disabled. For a single user's automation, a restricted developer key is usually simpler.