Getting An Email Of User Information
Hello team,
Is it possible to have the agent capture the user information and have that sent to my email?
If so how?
What would be a reason that the Google sheets functions is not working, also can the agent be integrated with Hunger Rush Manual POS?
How can the agent answer smarter customer service questions (from the knowledge base), and provide a sentences responses, not a whole paragraph like ChatGPT?
2 Replies
Here’s how you can do each of those things in Voiceflow
1️⃣ Collect user info and email it to yourself
• Use Capture / Form blocks (or variables you collect in-conversation) to store the user’s name, email, order, etc.
• Add an Agent → Gmail → “Send email” action right after the capture.
– OAuth-connect your Gmail the first time.
– Map the variables you just captured into the Body or Subject fields.
– Put your own address in the To field.
Result: every time the flow reaches that step you receive an email with the user details.
Docs: https://docs.voiceflow.com/update/docs/integrations#gmail 2️⃣ Google Sheets action not working – common checks • Make sure the workspace member who connected Sheets still has access to that Google account (re-connect if the token expired).
• The action must receive every required field (
• The bot must have edit permission on the sheet. Use Share → Anyone with link can edit during testing. 3️⃣ HungerRush (manual POS) integration Voiceflow doesn’t have a native HungerRush connector today. Teams typically handle this by:
• Calling a REST/Webhook endpoint exposed by HungerRush (via a Code block or a Make/Zapier scenario), or
• Writing a small middleware that receives the Voiceflow request and pushes it to the POS API.
If HungerRush exposes an API you can hit it from a Voiceflow Code step or Make → Run scenario action. 4️⃣ Make answers shorter / more “sentence-sized” Inside your Agent settings open Instructions and add something like:
• Add an Agent → Gmail → “Send email” action right after the capture.
– OAuth-connect your Gmail the first time.
– Map the variables you just captured into the Body or Subject fields.
– Put your own address in the To field.
Result: every time the flow reaches that step you receive an email with the user details.
Docs: https://docs.voiceflow.com/update/docs/integrations#gmail 2️⃣ Google Sheets action not working – common checks • Make sure the workspace member who connected Sheets still has access to that Google account (re-connect if the token expired).
• The action must receive every required field (
Spreadsheet ID, Sheet, etc.). Blank or mis-spelled column headers will cause silent failures.• The bot must have edit permission on the sheet. Use Share → Anyone with link can edit during testing. 3️⃣ HungerRush (manual POS) integration Voiceflow doesn’t have a native HungerRush connector today. Teams typically handle this by:
• Calling a REST/Webhook endpoint exposed by HungerRush (via a Code block or a Make/Zapier scenario), or
• Writing a small middleware that receives the Voiceflow request and pushes it to the POS API.
If HungerRush exposes an API you can hit it from a Voiceflow Code step or Make → Run scenario action. 4️⃣ Make answers shorter / more “sentence-sized” Inside your Agent settings open Instructions and add something like:
“When responding, keep answers to 1–2 concise sentences unless a longer explanation is absolutely required.”You can also set max_tokens under LLM Advanced Settings to a lower value (e.g. 60) to enforce brevity. Hope this clears things up – let me know if you need more detail on any step!
Voiceflow
Integrations
Supercharge your agent's capabilities with integrations to external apps and tools.
In number 3 about Hunger Rush, should the business owner have their own custom API Key or would should that be with hunger rush