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

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

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

Google Meet
⚙
Kintone
Authenticate Kintone
Now, click the Kintone node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Kintone settings. Authentication allows you to use Kintone through Latenode.
Configure the Google Meet and Kintone 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 Meet and Kintone 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
⚙
Kintone
Trigger on Webhook
⚙
Google Meet
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring Google Meet, Kintone, 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 Meet and Kintone integration works as expected. Depending on your setup, data should flow between Google Meet and Kintone (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Google Meet and Kintone
Google Meet + Slack + Kintone: When a Google Meet call ends, a Slack notification is sent with a link to the meeting summary (assuming a summary is generated and available). The corresponding Kintone record is then updated with this summary link.
Kintone + Google Calendar + Google Meet: When a new record is created in Kintone, a Google Calendar event is created. This event automatically includes a scheduled Google Meet call.
Google Meet and Kintone integration alternatives
About Google Meet
Automate Google Meet within Latenode workflows. Schedule meetings based on triggers, automatically generate invites after form submissions, or record & transcribe calls, saving time and ensuring consistent follow-up. Connect Meet to CRMs or project tools for streamlined task management. Simplify repetitive scheduling and meeting-related tasks.
Similar apps
Related categories
About Kintone
Integrate Kintone into Latenode to automate custom application workflows. Sync data, trigger actions, and manage processes without code. Extend Kintone's capabilities with Latenode's visual builder, JavaScript functions, and AI tools to automate data validation, reporting, and notifications. Scale efficiently and only pay for what you use.
Related categories
See how Latenode works
FAQ Google Meet and Kintone
How can I connect my Google Meet account to Kintone using Latenode?
To connect your Google Meet account to Kintone on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Google Meet and click on "Connect".
- Authenticate your Google Meet and Kintone accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Kintone records from Google Meet transcripts?
Yes, you can! Latenode's AI blocks parse meeting transcripts, extracting key data to populate new Kintone records. Improve data capture and streamline follow-ups.
What types of tasks can I perform by integrating Google Meet with Kintone?
Integrating Google Meet with Kintone allows you to perform various tasks, including:
- Automatically creating Kintone records for new meeting attendees.
- Sending Google Meet invites based on Kintone record updates.
- Logging meeting summaries in Kintone after each Google Meet session.
- Triggering Google Meet calls directly from Kintone application records.
- Updating Kintone records with files shared during Google Meet sessions.
How do I handle time zone differences between Google Meet and Kintone?
Latenode offers built-in functions and JavaScript support for seamless time zone conversions, ensuring accurate scheduling across platforms.
Are there any limitations to the Google Meet and Kintone integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex Kintone data structures may require custom JavaScript for data transformation.
- Google Meet API rate limits may affect high-volume automation workflows.
- Real-time bi-directional synchronization isn't supported; data updates are periodic.