Meet

Meet Component

The Meet component acts as a bridge between your Nappai workflows and the Google Meet platform. It allows you to interact with videoconference meetings programmatically. You can use this component to retrieve meeting details, check the status of a session, manage participants, or prepare meeting links for automated triggers.

This component simplifies complex Google Meet interactions by providing a structured interface where you only need to provide the necessary details (like calendar ID or meeting ID), and the system handles the communication with the Google Meet API in the background.

How it Works

This component connects directly to the Google Meet API. When you configure the component in your dashboard, it sends your input parameters to Google’s servers to perform specific actions, such as fetching meeting information or validating a conference ID.

The component relies on a Credential to authenticate with Google Meet securely. Once connected, it processes your requests and returns structured data that you can use in subsequent steps of your workflow. For example, if you check a meeting’s status, the component will return success or error details that you can map to other actions, such as sending a notification if a meeting is not found.

Connection & Credentials

This component requires configuring a Google Meet credential before you can use it. Credentials store the secure authentication details needed to access your Google Meet data.

Go to the Credentials section in your Nappai panel.
Create a new credential of the type Google Meet and fill in the required fields:
- Select Project: Choose your Google Cloud project.
- Client Id: Enter your Google Cloud Project Client ID.
- Client Secret: Enter your Google Cloud Project Client Secret.
- Google Meet access: Select the appropriate access level.
In your workflow, select the saved credential in the Credential input field of this node.

Note: Ensure your Google Cloud Project has the Google Meet API enabled and OAuth 2.0 consent screen configured correctly.

Inputs

The following fields are available to configure this component. You can map data from other components or enter values manually.

Operation: Select the action to perform. This dropdown determines how the component behaves.
Input Type: Choose the method to provide input. If Id is selected, the input will be the ID of the calendar. If Selection is selected, the input will be a dynamic selection.
Calendar Id: The unique identifier for the calendar. If not provided, the primary calendar will be used.
Calendar Selection: A dropdown to select a calendar from your Google Calendar account.
Conference ID: The conference ID of your meeting conference. In retrieval operations, if left empty, all conferences will be returned.
Start: The start time of the range. Must be in the format YYYY-MM-DD HH-MM-SS AM/PM TZ.
End: The end time of the range. Must be in the format YYYY-MM-DD HH-MM-SS AM/PM TZ.
Limit: The maximum number of results to return. Default is 10.
Credential: Select the Google Meet credential configured in your Nappai panel.

Outputs

This component produces a Data output that contains the result of the operation. You can map this output to other components to further process meeting information, such as logging details or triggering alerts.

Output Data Example (JSON)

Below is an example of the structured data returned by the component upon a successful operation. This data can be accessed by subsequent nodes in your workflow. json { “status”: “success”, “meeting_data”: { “id”: “abc123def456”, “link”: “https://meet.google.com/abc-123-def”, “start_time”: “2023-10-27 10:00:00 AM UTC”, “end_time”: “2023-10-27 11:00:00 AM UTC”, “participants”: [ “user1@example.com”, “user2@example.com” ] }, “raw_response”: { “kind”: “meet#conferenceData”, “entryPoints”: [ { “entryPointType”: “video”, “uri”: “https://meet.google.com/abc-123-def” } ] } }

Connectivity

The Meet component is designed to fit seamlessly into automation workflows involving videoconferences and calendar management.

Typical Connections:
- Incoming: Connects from a Scheduler (to check meetings at specific times), a Form input (to process a user-provided meeting ID), or another Calendar component that generates calendar IDs.
- Outgoing: The Data output can be connected to:
  - Email/SMS Components: To notify participants based on meeting status.
  - Log Components: To audit meeting details or track attendance.
  - Conditional Branches: To route workflows based on whether a meeting exists or if an error occurred.
  - Database/CRM Components: To store meeting records or participant lists in external systems.

Usage Example

Scenario: Automated Meeting Status Check

You want to automatically check if a specific meeting is active and send a reminder to participants if it is.

Add the Meet Component to your workflow.
Credential: Select your configured Google Meet credential.
Operation: Choose the appropriate action to check meeting details.
Input Type: Select Id to use a specific identifier.
Conference ID: Enter the ID of the meeting you want to check (e.g., abc123).
Start/End: Optionally define a time range to narrow down the search.
Run/Execute: The component queries Google Meet.
Connect Output: Map the Data output to an Email component. Configure the email to include the meeting_data details only if the status indicates success.

This setup allows you to automate reminders or status updates without manually checking Google Meet every time.

Tips and Best Practices

Time Format Accuracy: When using the Start and End inputs, ensure the time format strictly follows YYYY-MM-DD HH-MM-SS AM/PM TZ. Incorrect formatting may cause validation errors.
Use Mappings: When possible, use mapped inputs to dynamically pass calendar IDs or meeting IDs from other components. This makes your workflows more flexible and reusable.
Handle Errors: The component returns structured status information. Use conditional logic in your workflow to handle cases where a meeting is not found or an API error occurs.
Credential Management: Keep your Google Meet credentials secure. Rotate credentials periodically if your Google Cloud policy requires it.
Limit Results: If you expect a large number of results, use the Limit input to control the number of items returned, which can improve workflow performance.

Security Considerations

Credential Storage: Credentials are stored securely in Nappai and are never exposed in logs or output data.
API Access: Ensure your Google Cloud Project has the necessary permissions enabled for the Google Meet API.
OAuth Consent: Verify that your OAuth consent screen is configured to allow access to the required scopes for meeting management.
Data Privacy: The component retrieves meeting data based on the authenticated user’s context. Ensure you have the appropriate permissions to access the targeted meetings.