Hi everyone, I hope you are all doing well and enjoying the AI journey. My clone has helped me build an operating agent under GPTs to manage my business tasks, and to achieve this, it guided me to connect my Google Calendar to the agent and then build an automation in Make.com to process my instructions into event actions. My goal is for my agent to automatically: - create - update - move - delete events in my Google Calendar using only natural-language instructions. To achieve this, my clone guided me to build an automation in Make.com: 1. Webhook receives the instruction text 2. OpenAI converts the instruction into clean JSON (with action, summary, start, end, timezone) 3. JSON Parser extracts the fields 4. Google Calendar is supposed to create the event Everything works until the final step.Google Calendar keeps returning this error: BundleValidationError: Missing value for ‘summary’ and missing value for ‘start’. Even though the JSON parser clearly shows: - summary - start - end - timezone So the Google Calendar module is not receiving the values. I would like to ask the community and the AIA Team: 1. Will the Bootcamp sessions cover agent automation? Especially automations that connect an agent to tools like Google Calendar through Make.com, Zapier, or similar tools. 2. Is there any easy or recommended method to let my agent update Google Calendar? If Make.com is not reliable, is there a simpler or preferred approach within GPTs or using different automation platforms? 3. Is anyone here successfully managing their Google Calendar through their clone or agent? If yes, could you please share the steps, template, or solution you used? 4. Are there any official materials, templates, or documentation about connecting agents to create, update, or delete Google Calendar events using natural-language instructions? This automation is very important for my business, and I know someone here may have solved a similar challenge.

It's always hard to practice overcoming objections, so I built a chatbot to learn to do so for free. So fun! What are you building?

Hi I’m an entrepreneur relatively new to AI and so thankful for the great info the AI Advantage shared! (for a few years I’ve been using Chat GPT for the basics). My team recently created a template webpage to market our services, and it’s very basic but I want to use AI to add features for lead generation; inserting a contact form and generating email responses to each enquiry etc. How do I add all this to my webpage the short way with AI?

A lot of AI safety talk gets stuck in “it’s complicated.” It doesn’t have to be. If you’re building with AI (even if you’re not technical), you can reduce risk a lot with a few default habits—the same way we made cars safer with seatbelts, rules of the road, and inspections. 1) Who teaches this? Not “the government.” Not “experts on Twitter.” You + your builder + your tools. Think of it like “AI driver’s ed”: - 20% is mindset (responsibility) - 80% is checklist + routines (what to do every time) 2) How should it be taught? Not by fear. Not by theory. By simple checklists + examples. If you can follow a recipe, you can follow this. ✅ The Non-Tech Guardrails Checklist (print this) A) Secrets & passwords (most common failure) - Use two-factor authentication on everything - Don’t paste API keys into screenshots or chats - Store keys in a proper “secrets” place (your dev will know) - If something feels off: rotate keys (replace them) B) Updates (the boring part that saves you) - If your app is public: ask your dev:“Do we patch security updates weekly?” - If you don’t have a dev: use managed platforms that update for you. C) Logs (so you can see trouble early) Ask: “Do we have logs turned on?” If the answer is “not really,” you’re flying blind. D) Ownership (someone must be responsible) For every AI feature ask: - “Who owns this if it breaks?” - “Who gets alerted?” - “What’s the rollback plan?” E) Kill-switch (simple off button) Every AI feature needs a way to pause it: - “Can we turn it off in 1 minute if needed?” 3) How do we “pressure” the world to do better? You don’t need to lobby governments to make progress. The fastest levers are: - Customer expectations (“we only buy tools with safety basics”) - Platform defaults (secure-by-default settings) - Procurement rules (“no guardrails = no contract”) - Community standards (we normalize checklists) Bottom line Cheerleaders can cheer. Builders can build.