← Back to all posts

Google Meet

On this page

Purpose

Google Meet runs actions from a Composio-connected Google account. Agent Core can use the enabled Meet tools, or a normal flow can run one selected action.

When to use it

  • Create or inspect a meeting space when the connected toolkit offers that action.
  • Retrieve conference records.
  • Give an Agent a narrowly scoped meeting capability.

Required setup

  1. Create a Composio project API key in Composio Settings > Project Settings > API Keys. Add it in the component or select a saved Arkus Credential. Never put it in prompts, examples, or images.
  2. Use the component authorization flow to connect the Google Meet account. This provider grant is separate from the Composio key. The auth config chooses OAuth or API-key authentication and requested scopes. A workspace or organization administrator may need to approve permissions.
  3. When the connected account is active, Arkus loads available actions. Selected actions become separate Agent tools. The Google Meet toolkit page shows the catalog beyond this guide. Actions can vary by connected account and the toolkit version pinned by Arkus. The examples below are not exhaustive.
  4. Missing actions? Check the Composio key, connected-account status, requested scopes, and administrator approval. Then reconnect or refresh.

How to use it

Tool Mode

  1. Add Google Meet, select the saved Composio Credential, and complete the account connection.
  2. Enable Tool Mode, keep only the Actions the Agent needs, and connect the tool output to Agent Core.
  3. Test a read-only action before enabling meeting changes.

Normal mode

  1. Choose one Action and provide its inputs.
  2. Connect the DataFrame output to the next step.

Configuration

SettingWhat it controlsRecommended starting point
Composio API KeyConnects Arkus to Composio and loads the action schema.Select a saved Credential.
ActionChooses one available Meet action in normal mode.Start with a read-only action.
Auth ModeAppears when the connected toolkit requires an authentication choice.Use the mode required by the authorized account.
ActionsSelects loaded actions that become separate Agent tools in Tool Mode. Builder can curate any relevant subset. Without a selection or component default, Arkus starts with the first five fetched actions.Review the initial set and keep only the meeting actions the Agent needs.
Entity IDIdentifies the editor-side Composio user. Deployed flows use the authorized owner instead.Leave default in normal Builder use.

Expected result

Tool Mode gives Agent Core the enabled Meet tools. Normal mode returns a DataFrame. A deployed flow requires a saved owner Composio Credential and exactly one active owner account. If the account is missing, disabled, or ambiguous, Arkus asks the owner to reconnect before execution. Authorization failures during an action return a provider error.

Reference details

Actions do not run automatically. In an Agent workflow, the Agent can call only the actions you expose.

Works well with

Use Google Meet with Google Calendar in Agent Tool Mode when the workflow needs to coordinate calendar and meeting information.

← Back to all posts