New-visitor follow-up workflow

Setup guide.

Step-by-step from “fresh install” to “first run.” Skim it once, then keep this page open while you go.

Before you import

This workflow connects four services. Open each one in a separate browser tab so you can copy credentials without losing your place: n8n, Brevo, Telegram (Web or BotFather), and Tally.

Step 1 — Import the JSON into n8n

Download the new-visitor-followup.json from the Quick Install button above. In n8n, click Workflows → Import from file and select the JSON. The four nodes (Tally webhook, Brevo, Telegram, Google Calendar) appear, all marked red until you wire credentials.

Step 2 — Wire Brevo

Open Brevo → SMTP & API → Generate a new API key with the Contacts scope. In the Brevo node in n8n, paste it as an httpHeaderAuth credential with header name 'api-key'. Replace REPLACE_WITH_NEW_VISITORS_LIST_ID with your list's numeric ID (Brevo → Contacts → Lists shows it next to the list name).

Step 3 — Wire Telegram (optional but recommended)

Talk to @BotFather on Telegram and create a bot if you don't already have one. Add the bot to your pastoral-care channel and look up the channel's chat_id (the @userinfobot helper works, or check the channel info in Telegram Desktop). Replace REPLACE_WITH_TELEGRAM_CHAT_ID in the Telegram node parameters.

Step 4 — Point your Tally form's webhook at n8n

In Tally → your form → Integrations → Webhooks, paste the n8n webhook URL (visible on the Tally webhook node in n8n). Send a test submission to confirm the workflow runs end-to-end: Brevo logs a new contact, Telegram pings the channel, and (if wired) Google Calendar drops the coffee invite.

Troubleshooting.

Hit one of these? Here's the fix.

Brevo returns 401 Unauthorized

Confirm the API key has the Contacts scope (not just SMTP). Brevo issues separate scopes per surface — generating a key from the SMTP page only gives you mail-sending permission, not contact CRUD.

Telegram says 'Forbidden: bot was kicked from the channel'

Re-add the bot to your channel and ensure it has the 'Post messages' admin permission. Channels are stricter than groups — bots need explicit channel-admin rights to post.

Tally form submission doesn't reach n8n

Check that the n8n workflow is Active (not just saved). The webhook URL only accepts POSTs while the workflow is on. Also confirm the Tally webhook integration is set to fire on 'Form submitted' (not 'Form viewed').