Grain Tools

Grain captures, transcribes, and summarizes your meeting recordings. Use these tools in a workflow to list and fetch recordings, pull full transcripts and AI-generated summaries, browse views/teams/meeting types, and manage webhooks that notify your workflow when recordings change.

Overview

Operations

Configuration

All operations authenticate with a Grain API key (Personal Access Token), sent as a Bearer token in the Authorization header. The apiKey parameter is a secret — store it as an environment variable and reference it with {{...}} rather than hard-coding it.

grain_list_recordings

grain_get_recording

grain_get_transcript

grain_list_views

grain_list_teams

grain_list_meeting_types

grain_create_hook

grain_list_hooks

grain_delete_hook

Outputs

grain_list_recordings

• recordings (array) — Array of recording objects
• cursor (string, optional) — Cursor for the next page

grain_get_recording

• id (string) — Recording UUID
• title (string) — Recording title
• url (string) — URL to view in Grain
• duration_ms (number) — Duration in milliseconds
• participants (array, optional) — Participants list
• ai_summary (json, optional) — AI summary

grain_get_transcript

• transcript (array) — Array of transcript sections with speaker, text, and start/end times

grain_list_views

• views (array) — Array of view objects

grain_list_teams

• teams (array) — Array of team objects with id and name

grain_list_meeting_types

• meeting_types (array) — Array of meeting type objects

grain_create_hook

• id (string) — Hook ID
• hook_url (string) — Webhook URL
• enabled (boolean) — Whether the hook is enabled

grain_list_hooks

• hooks (array) — Array of webhook objects

grain_delete_hook

• success (boolean) — Whether the hook was deleted

YAML Example

grain_1:
  type: grain
  name: "Grain"
  inputs:
    operation: "grain_list_recordings"
    apiKey: "{{GRAIN_API_KEY}}"
    afterDatetime: "2024-01-01T00:00:00Z"
    includeAiSummary: true
  connections:
    outgoing:
      - target: next-block-id

Tips

• Auth setup: Generate a Personal Access Token in your Grain account settings and store it as an environment variable (e.g. GRAIN_API_KEY), then reference it with {{GRAIN_API_KEY}}. Every operation requires it. Requests are sent against https://api.grain.com/_/public-api/v2 with the Public-Api-Version: 2025-10-31 header.
• Pagination: grain_list_recordings returns a cursor when more results exist. Pass it back as the cursor parameter to fetch the next page.
• Rich data is opt-in: The includeHighlights, includeParticipants, includeAiSummary, includeCalendarEvent, and includeHubspot switches default to off — enable only what you need to keep responses small. Transcripts come from the separate grain_get_transcript operation.
• Webhooks need a view: grain_create_hook requires a viewId to scope events; use grain_list_views to find one. When actions is omitted, the hook subscribes to added, updated, and removed events.