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

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

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

Google Dialogflow ES
⚙
Moco
Authenticate Moco
Now, click the Moco node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Moco settings. Authentication allows you to use Moco through Latenode.
Configure the Google Dialogflow ES and Moco 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 Dialogflow ES and Moco 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
⚙
Moco
Trigger on Webhook
⚙
Google Dialogflow ES
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring Google Dialogflow ES, Moco, 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 Dialogflow ES and Moco integration works as expected. Depending on your setup, data should flow between Google Dialogflow ES and Moco (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Google Dialogflow ES and Moco
Google Dialogflow ES + Moco + Google Sheets: When a user interacts with a Dialogflow ES chatbot and an intent is detected, the details of the interaction are logged in a Google Sheet. Additionally, when project time is logged in Moco, it's also recorded in the same Google Sheet, allowing for a consolidated view of chatbot interactions and project time.
Moco + Google Dialogflow ES + Slack: When new project time is logged in Moco, the automation triggers a Dialogflow ES intent to summarize project status. The summary generated by the chatbot is then sent to a designated Slack channel, providing a quick overview of project updates to the team.
Google Dialogflow ES and Moco integration alternatives
About Google Dialogflow ES
Use Google Dialogflow ES in Latenode to build smart chatbots and automate customer service tasks. Connect Dialogflow to your databases, CRMs, or other apps for personalized responses. Create visual workflows that handle complex conversations without code, adding custom logic with JavaScript where needed. Scale your AI-powered interactions using Latenode's flexible automation platform.
Similar apps
Related categories
About Moco
Use Moco in Latenode to track time and expenses. Automate reporting, invoice creation, and project budget monitoring. Connect Moco to accounting or CRM systems for streamlined financial workflows. Build flexible, customized solutions without code, and scale automations as your business grows inside Latenode's visual environment.
Related categories
See how Latenode works
FAQ Google Dialogflow ES and Moco
How can I connect my Google Dialogflow ES account to Moco using Latenode?
To connect your Google Dialogflow ES account to Moco on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Google Dialogflow ES and click on "Connect".
- Authenticate your Google Dialogflow ES and Moco accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I track billable hours from Dialogflow conversations in Moco?
Yes, you can! Latenode lets you parse conversation data using AI and automatically log billable hours in Moco, streamlining time tracking and invoicing with ease.
What types of tasks can I perform by integrating Google Dialogflow ES with Moco?
Integrating Google Dialogflow ES with Moco allows you to perform various tasks, including:
- Automatically create Moco projects based on intent detected in Dialogflow.
- Log time entries in Moco based on conversation duration.
- Update client information in Moco based on Dialogflow data.
- Send Moco project updates via Dialogflow chatbot responses.
- Trigger Moco invoice creation when a Dialogflow goal is reached.
How can I use JavaScript to enhance my Google Dialogflow ES automations?
Latenode allows you to use JavaScript code blocks to manipulate data from Dialogflow ES for advanced routing and transformation before sending it to Moco.
Are there any limitations to the Google Dialogflow ES and Moco integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex Dialogflow ES intent structures might require custom JavaScript parsing.
- Moco API rate limits may affect high-volume data transfers.
- Custom field mapping requires careful configuration during setup.