How to connect Google Chat and Delighted
Create a New Scenario to Connect Google Chat and Delighted
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 Google Chat, triggered by another scenario, or executed manually (for testing purposes). In most cases, Google Chat or Delighted will be your first step. To do this, click "Choose an app," find Google Chat or Delighted, and select the appropriate trigger to start the scenario.

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

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

Google Chat
⚙
Delighted
Authenticate Delighted
Now, click the Delighted node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Delighted settings. Authentication allows you to use Delighted through Latenode.
Configure the Google Chat and Delighted 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 Google Chat and Delighted 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
⚙
Delighted
Trigger on Webhook
⚙
Google Chat
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring Google Chat, Delighted, 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 Google Chat and Delighted integration works as expected. Depending on your setup, data should flow between Google Chat and Delighted (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Google Chat and Delighted
Delighted + Google Sheets + Google Chat: When a new response is received in Delighted, the response data is added as a new row in a Google Sheet for tracking customer satisfaction trends. A summary of the response is then sent to a Google Chat space.
Delighted + Jira + Google Chat: When a new response is received in Delighted, the system checks if the response is negative. If so, a Jira ticket is created, and a notification is sent to a Google Chat space to alert the team.
Google Chat and Delighted integration alternatives
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
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
See how Latenode works
FAQ Google Chat and Delighted
How can I connect my Google Chat account to Delighted using Latenode?
To connect your Google Chat account to Delighted on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Google Chat and click on "Connect".
- Authenticate your Google Chat and Delighted accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I get Google Chat notifications for low Delighted survey scores?
Yes, you can! Latenode lets you trigger Google Chat messages based on Delighted survey scores. React instantly to negative feedback and improve customer satisfaction using automated workflows.
What types of tasks can I perform by integrating Google Chat with Delighted?
Integrating Google Chat with Delighted allows you to perform various tasks, including:
- Send new Delighted survey responses to a Google Chat channel.
- Create alerts in Google Chat for negative Delighted survey scores.
- Share positive Delighted feedback in a dedicated Google Chat room.
- Automatically thank survey respondents in Google Chat.
- Escalate critical Delighted feedback from Google Chat to support.
Can I customize survey notifications within Google Chat on Latenode?
Yes! Latenode’s JavaScript code blocks provide advanced customization. Tailor Google Chat messages with survey data for relevant context.
Are there any limitations to the Google Chat and Delighted integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex logic may require custom JavaScript for advanced workflows.
- Google Chat API rate limits may affect high-volume notification flows.
- Historical Delighted data may not be easily migrated via the integration.