Hi everyone, I am using WhatsApp Cloud API directly from Meta. Right now: - My app is in Development mode - I am using the Meta provided test phone number - Messaging works fine with the test number on n8n I have a few simple questions: 1. For real production usage (real WhatsApp number and real users), do I need to switch the app to Live mode? 2. Is the access token shown in the Quickstart / API Setup page only a temporary token and not recommended for production? 3. To get a permanent (non-expiring) access token, do I only need to switch app to Live mode or there is something else to do? 4. For automation, is it recommended to use a fresh/new WhatsApp number instead of an existing WhatsApp number? I want to be sure I am following the correct and safe process before going live. Thanks for your help.

Hey everyone 👋 A few days ago, I shared a quick walkthrough of a system I built called TalkPilot. After that post, I started getting a lot of messages asking for a proper demo — how it actually behaves in real time and how it handles different scenarios. So I recorded a full working demo showing the complete flow. You can watch it here: https://www.linkedin.com/posts/yash-maheshwari5_youre-losing-leads-even-though-people-activity-7422560191121944576-JUGF In this demo, I walk through how the system handles conversations from start to end. Some of the key things it covers: • identifies new vs existing leads using email • avoids duplicate entries in the CRM • remembers previous conversations and shows them with dates • allows notes to be added at any point and maintains a history of past notes • supports human approval for sensitive cases like discounts • allows users to update incorrect details (like email) • answers only business-related questions and ignores irrelevant ones • handles meeting booking, rescheduling, and cancellation • manages time zones correctly for both user and admin • sends automated reminders before meetings (24h and 30min) • tracks show and no-show scenarios • sends feedback or reschedule follow-ups automatically • maintains structured chat history and summarized conversation records This post is mainly to share the working demo and the overall thinking behind the system. In the upcoming videos, I’ll be breaking down how this system is developed — the logic, automation flow, and structure behind it. Would love to hear thoughts or suggestions from people building similar systems.

Hey everyone 👋 I’ve been working on an automation system recently and wanted to share it here to get some genuine feedback. Most chat systems I’ve seen are good at replying — but once conversations continue, things start breaking: users return, details change, meetings get rescheduled, timezones create confusion, and follow-ups don’t happen properly. So I built something called TalkPilot. The goal wasn’t to create another chatbot, but a system that can actually manage conversations end to end. It can: • remember users and past conversations • update details naturally during chat • book, reschedule, or cancel meetings • handle everything in the user’s timezone • send reminders automatically • ask for feedback after meetings • handle no-shows with reschedule links I’ve shared a short overview video on LinkedIn showing how the system looks in action. 👉 Watch here: https://www.linkedin.com/posts/yash-maheshwari5_problem-most-businesses-rely-on-chat-systems-ugcPost-7418271469211865088-RRt9 This is just an overview — next I’ll be sharing how the whole system is built behind the scenes. Not selling anything here, just building and learning in public. Would genuinely love to hear your thoughts or suggestions 🙌

This is my first post here, so I wanted to share something I recently built and get your feedback. I just completed an end-to-end automation system using Jotform, Make, Salesforce, and GoHighLevel. What this system handles: - New lead intake from Jotform - Automatic Salesforce checks (existing applicant or new) - Household creation when a spouse is involved - Auto-attachment of Jotform PDFs to the correct applicant - Backend document uploads auto-attached to Salesforce - GoHighLevel handling follow-ups, SMS, emails, emails, and pipeline updates The main goal was to eliminate manual work, avoid duplicate records, and make follow-ups fully reliable. I’m sharing: - Workflow images (logic + scenarios) - LinkedIn post link: https://www.linkedin.com/posts/yash-maheshwari5_today-i-want-to-share-a-automation-system-activity-7414265293692153856-RQjb?utm_source=share&utm_medium=member_desktop&rcm=ACoAADVOdbgBS1rmSmlKuqAwaxmU8y3VEyx4HzU Would genuinely love feedback on: - System design - Logic flow - Anything you’d improve or simplify Appreciate being part of this community 🙌

Hi, I'm trying to send the record ID from Salesforce to Make.com based on a specific condition using a webhook. It’s almost working, but not always accurately. I’m using Salesforce Flow Builder for this. If you have experience with Salesforce, I’d really appreciate your help. Thanks!