Design a reservation request workflow

Design a reservation request workflow for [restaurant]. Ask for guest name, party size, preferred date/time, and contact method. Discover available date/time, validation, calendar, and database nodes. Use [business timezone] explicitly. Show how an availability check could work with my selected calendar, but do not connect a paid service or create a reservation. Make the wording distinguish received request, availability checked, and booking confirmed. Include invalid-input, no-availability, and connection-error paths. Report the account and table setup still needed.

Use the Chatigram plugin for organization [organization name]. Discover the current permissions, plan limits, triggers, node types, and compatible connections before designing the solution. For conversation workflows, check the selected Line’s Private AI mode before proposing Inbox follow-up or a human handoff. Do not promise human access to private AI conversations. Prepare and save the requested workflows disabled, after showing the draft preview and any unresolved setup. Do not activate, run, assign to a live Line, send messages, or use paid processing. If a paid capability or connection is needed, explain the service, account, transferred data, and required spending approval before adding or binding it. Do not ask me to paste credentials into chat; use protected setup links. Keep unrelated resources unchanged.

Finish with: what was prepared, what is still missing, which plan-dependent features are involved, and the next safe test. Do not claim execution or delivery from a draft preview.