The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Switch nodes + Redis nodes are underrated when building chatbots.
In my opinion, these two are some of the most useful nodes for building solid chatbot logic in n8n.
🔀 Switch nodes → help route conversations based on intent, conditions, user type, or previous messages.
⚡ Redis nodes → help maintain conversation state, store temporary data, and give the bot memory across messages.
Together, they make it much easier to build chatbots that go beyond simple “if this, then that” workflows.
What do you think?
Which n8n node do you find most useful when building chatbot logic? 👇
Good picks. One Redis detail worth getting right early: always set a TTL on the session keys — otherwise every conversation you've ever had stays in memory forever, context can leak between sessions, and memory costs creep up. Keying session state by chat ID with a rolling TTL...
Absolutely! 👏 TTL is one of those small details that makes a big difference in production. A rolling TTL with the chat ID as the session key is a great way to keep conversations isolated while preventing Redis from filling up with stale session data. Thanks for the insight!
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
You need a strong starting point for a sales-tech brand without trying too hard.
A generic SaaS template won’t work in this case.
What you need are:
• Sales-focused product UI
• Personalized outreach with follow-up and reply intelligence
• Pricing, testimonials, FAQs, and integrations
• CMS for blog posts, feature pages, and case studies
• Clear paths to demos and trials
That’s how we designed Avina, our new Framer template.
Built for AI sales products, outbound automation tools, and sales-focused SaaS products.
Avina is designed around a real outbound sales journey.
So visitors understand quickly.
Check the link in the comment.
What I like here is the focus on the actual sales journey, not just the visual design. For AI sales tools, showing how outreach, follow-ups, and reply handling connect to real outcomes can make a big difference. Curious how you approached that in Avina?
Just posted a new case study on Contra.
A 60-second promo for Ulta AI by Ultahost, a chatbot that runs a server through plain conversation. Script, storyboard and animation, all built around the real product UI.
Check it out
Let me know what you think💭😍
From packed boxes to a shipment the client can track.
This TechFoundry IMS demo reuses box details, retrieves UPS rates, creates shipping labels, and keeps tracking connected to the client order. A practical example of the AI and automation workflows we build into business software.
Watch the client shipping demo:
https://www.youtube.com/watch?v=8ohniU08JAA
#AI #Automation #SoftwareDevelopment #Shipping
I like that the shipment stays tied to the client order instead of living in a separate carrier tab. When box details get edited after the UPS rate is retrieved, does the system re-quote before creating the label, or lock the original rate? I'd be curious how you handle that mismatch on the tracking side.
