Integrationsn8n
Your calendar, shop or database starts the workflow, and the HTTP Request node sends name and number to Citypicked. We do the rest.
The HTTP Request node
This is how n8n shows the node when you open it. You create the automation link in Citypicked under Settings, Sending. Simply drag the fields from the node before it into the text.
What comes back
Citypicked answers every call with a status. So you already see in n8n whether the request goes out.
So that a refusal does not stop the workflow, set “On Error” to “Continue” under the node's Settings.
Where n8n runs
Nothing extra. The automation link comes with Pro. Texts use credits as in the app, emails none.
With delay_minutes Citypicked waits, an hour after the appointment for example. Outside your sending hours the request waits for the next ones.
Whatever you set on the link. If you send channel with sms or email, that applies to this one customer.
Run the node once. The test sends a real request, so best use your own number. Then activate the workflow.
Yes, for texts and emails. Best ask at booking or at checkout whether you may follow up.
Your first request goes out in five minutes.