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.

Hi all, I'm triggering Vapi outbound calls via n8n. Inbound works fine, but on Outbound, the agent ignores my n8n tools (Calendar/Booking). **The Blocker:** When using the `/call` API endpoint, does the `assistantId` automatically inherit the attached tools and Server URL, or do I need to hardcode them explicitly into the API JSON payload? If anyone has a working outbound JSON payload that successfully calls backend tools, please share. Stack: Vapi, n8n (Self-hosted).

Added: * error alerts * simple logging * daily glance check Zero surprises since.

Don’t start with “AI”. Start with a boring workflow. Ask:“What would I do manually if AI didn’t exist?” Then automate that. Simple example: - If form is submitted - Then clean the data - Then generate a short summary - Then save it somewhere Make.com handles: - the order - the rules - the failure cases AI just helps with one step. When I tried to design “smart AI systems” first, everything broke.When I designed clear workflows first, AI became easy to add. Hope this helps someone who’s feeling overwhelmed by tools.

What worked for me: 1. Explain the logic first. 2. AI second. 3. Show the boring parts it replaces. Way fewer confused conversations since.