Description

n8n-nodes-surveysparrow

n8n community nodes for SurveySparrow: share surveys through Email, SMS, and WhatsApp channels, create contacts, and trigger workflows on new survey submissions.

Install (community nodes)

In n8n: Settings → Community nodes → Install and enter:

n8n-nodes-surveysparrow

Or install manually in your n8n environment:

npm install n8n-nodes-surveysparrow

Restart n8n, then enable the package under Community nodes if your instance requires it.

Credentials

1. In SurveySparrow, create an OAuth application and note the Client ID and Client Secret.
2. Set the OAuth redirect / callback URL to your n8n OAuth callback (shown when you create credentials in n8n).
3. In n8n, create SurveySparrow OAuth2 API credentials and complete the sign-in flow.

OAuth and scopes are described in the SurveySparrow OAuth documentation.

Nodes

| Node | Purpose |
|——|———|
| SurveySparrow | Share surveys via Email / SMS / WhatsApp; create contacts |
| SurveySparrow Trigger | Start a workflow when a new survey submission is received |

Example Workflows

1 — Trigger a workflow on every new survey response

1. Add a SurveySparrow Trigger node and select your survey.
2. Activate the workflow — n8n registers a webhook automatically.
3. Every completed submission fires the trigger and passes the answers as JSON to the next node.

2 — Send a survey via Email when a HubSpot deal closes

1. Use a HubSpot Trigger (deal stage changed) as the start node.
2. Connect a SurveySparrow node, set Action to Send Survey, select Channel Type → Email, pick your survey and email channel, and map the contact’s email address.
3. The survey link is delivered automatically when a deal moves to “Closed Won”.

3 — Create a SurveySparrow contact from a Typeform submission

1. Use a Typeform Trigger as the start node.
2. Connect a SurveySparrow node, set Action to Create Contact.
3. Map the respondent’s email and name from the Typeform fields to the SurveySparrow contact fields.
4. Optionally use Additional Fields to map any extra properties.

Development (this monorepo)

cd n8n
npm install
npm run dev

Build for production:

npm run build
npm run lint

Automated checks (Creator Portal / CI)

Run the same checks n8n recommends before publishing or submitting for review (Test a node, Node linter):

npm test

This runs build then lint (eslint-plugin-n8n-nodes-base via n8n-node lint). To disable a rule for one line when you have a good reason, use an ESLint disable comment as described under Exceptions.

Optional: after the package is on npm, run n8n’s security scanner (also referenced in verification guidelines):

npm run test:security

Or npm run test:all for both.

Publish to npm

1. Log in: npm login (use an account allowed to publish this package name).
2. From n8n/: npm run build && npm run lint
3. npm publish --access public (use --access public if the package name is new to your npm user/org)

For automated releases and provenance, add a trusted publisher or NPM_TOKEN workflow as described in the n8n deploy docs.

License

MIT — see LICENSE.md.