Set up the pack
- As the workspace owner, open the Form’s Notifications → Automations. Enable response storage in the Form settings so the enquiry has a native Contact and Inbox timeline.
- Find Customer Follow-ups and choose the follow-up deadline, from 1 to 720 hours after submission. The default is 24 hours. The pack uses the existing Contact follow-up service and creates a one-time reminder owned by you.
- Map the customer email and optional name fields.
- To prepare acknowledgements, connect your own Google account with Gmail draft permission, select a verified, billed Gemini API connection, and explicitly approve sending this Form’s plain-text answers to that model.
- Optionally grant Sheets access and select the spreadsheet ID and tab. The Sheet is an output; it does not replace the Contact timeline.
- Enable and save the pack. Submit a synthetic enquiry first, review the native receipt and Google action result, then open Gmail to review and send the draft yourself.
GOOGLE_WORKSPACE_ENABLED, native response storage, and Contact follow-ups. Existing workspaces are opted out. Enabling the pack does not grant Google permissions or change existing notification, webhook, Google Contact, or email-campaign settings.
If you only want native follow-ups, turn off the Gmail draft and Sheets options. This mode does not require Google authorization or a Gemini connection.
What happens on a new enquiry
The existing Form submission flow creates the Contact, response, and Inbox message. The pack links a follow-up to that same thread and message. It does not create a second customer database or infer a new owner. If someone has assigned the thread to another operator, the receipt asks for an ownership review and skips the pack’s Google outputs rather than taking over their thread. When you enable drafts, Gemini receives only the approved Form’s bounded plain-text answers. Uploaded files, request metadata, credentials, mailbox history, meeting content, and Google-imported knowledge are excluded. The model proposes a short acknowledgement; Laravel chooses the mapped recipient and subject and creates the draft through the fixed Gmail drafts endpoint. The model cannot choose a tool, URL, recipient, or send operation. Google’sgmail.compose permission permits sending as well as draft management. This pack enforces draft-only behavior in the backend: its Gmail action only creates a draft. It provides no customer-send or draft-update operation. Existing Google OAuth verification requirements still apply to the scopes your application requests.