How to connect Delighted and Google Chat
Create a New Scenario to Connect Delighted and Google Chat
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Delighted, triggered by another scenario, or executed manually (for testing purposes). In most cases, Delighted or Google Chat will be your first step. To do this, click "Choose an app," find Delighted or Google Chat, and select the appropriate trigger to start the scenario.

Add the Delighted Node
Select the Delighted node from the app selection panel on the right.

Delighted
Configure the Delighted
Click on the Delighted node to configure it. You can modify the Delighted URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Google Chat Node
Next, click the plus (+) icon on the Delighted node, select Google Chat from the list of available apps, and choose the action you need from the list of nodes within Google Chat.

Delighted
⚙
Google Chat
Authenticate Google Chat
Now, click the Google Chat node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Google Chat settings. Authentication allows you to use Google Chat through Latenode.
Configure the Delighted and Google Chat Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Delighted and Google Chat Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
Google Chat
Trigger on Webhook
⚙
Delighted
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring Delighted, Google Chat, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Delighted and Google Chat integration works as expected. Depending on your setup, data should flow between Delighted and Google Chat (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Delighted and Google Chat
Delighted + Asana + Google Chat: When a new negative response is received in Delighted, a task is created in Asana to address the feedback, and a notification is sent to a Google Chat space to alert the support team.
Google Chat + Delighted + Zendesk: When a new message is posted in Google Chat indicating critical feedback related to a Delighted survey, a new Zendesk ticket is created, referencing the Google Chat message and the original Delighted survey to ensure prompt support action.
Delighted and Google Chat integration alternatives
About Delighted
Automate feedback loops with Delighted in Latenode. Send surveys post-interaction and instantly act on results. Route scores to your team's Slack, update records in your CRM, or trigger follow-ups based on sentiment. Build adaptable workflows with no-code tools, custom logic, and AI — all without per-step costs.
Related categories
About Google Chat
Use Google Chat in Latenode for automated notifications & alerts. Trigger messages based on events in other apps, like new database entries or payment confirmations. Centralize alerts and status updates across services within a single, scalable Latenode workflow. Add custom logic and AI for smart notifications.
Related categories
See how Latenode works
FAQ Delighted and Google Chat
How can I connect my Delighted account to Google Chat using Latenode?
To connect your Delighted account to Google Chat on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Delighted and click on "Connect".
- Authenticate your Delighted and Google Chat accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I get survey responses in Google Chat?
Yes, you can! Latenode lets you forward Delighted survey responses to Google Chat. This ensures your team sees feedback in real-time, enabling immediate action and improved responsiveness.
What types of tasks can I perform by integrating Delighted with Google Chat?
Integrating Delighted with Google Chat allows you to perform various tasks, including:
- Receive new Delighted survey responses directly in a Google Chat channel.
- Send customized Google Chat notifications based on Delighted survey scores.
- Create tasks in other apps from negative Delighted feedback via Google Chat commands.
- Alert specific team members in Google Chat about critical Delighted feedback.
- Aggregate Delighted feedback summaries into a daily Google Chat digest.
Can I filter Delighted survey responses before sending to Google Chat?
Yes, with Latenode, you can filter responses based on score or keywords before forwarding them. This prevents information overload and ensures relevant notifications.
Are there any limitations to the Delighted and Google Chat integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex logic might require JavaScript knowledge.
- Rate limits apply based on your Delighted and Google Chat plans.
- Historical data sync requires custom implementation.