Keap Contact Updated? Auto-Sync It to Telegram
Whenever an existing Keap contact changes, this n8n workflow detects it and has Telegram send a Telegram message — keeping both tools in step automatically.
- 1
Fetch Keap data
Add an
HTTP Requestnode (or the native Keap node if you have credentials set up) and point it at the Keap API. Poll Keap for contact changes. Add aSchedule Triggerbefore it if this recipe runs on a timer, or aWebhooknode if Keap can push events directly. - 2
Shape the data with a Set node
Add a
Setnode after the fetch step to pull out the fields you need — e.g.id,title(orname),status, andupdated_atfrom the Keap contact. This keeps the rest of the workflow clean and readable. - 3
Send it to Telegram
Add a
Telegramnode set to operationSend Message. Connect your bot token and setChat ID, then buildTextfrom the Set-node fields. - 4
Activate and test
Click
Activatein the top-right corner. Trigger a real contact in Keap (or run the workflow manually against existing data) and confirm it lands correctly in Telegram. Once verified, this runs hands-off.
Frequently asked questions
Do I need to code anything?
No. n8n is a visual, drag-and-drop builder. You connect your Keap and Telegram accounts, map the fields, and activate — no code required.
Where do I get my Keap API credentials?
In your Keap account settings, look for "API", "Developers" or "Integrations" and generate an API key or token. Paste it into n8n's HTTP Request node (as a header or credential) or the native Keap node if one is available.
Can I filter which items trigger this workflow?
Yes. Add an `IF` node after the Set node with a condition on any field (status, amount, tag, etc.). Wire the TRUE branch to the Telegram step and leave FALSE empty to skip the rest.
Keep every recipe free
FlowRecipesHub is free and always will be. If a workflow saved you time, chip in what you like — it helps us keep the lights on and build the next batch of automations for everyone.
Secure checkout via Paddle · one-time, no account needed
