Integration
Connect Particle to Google Meet
When something happens in Particle, your agent does the next thing in Google Meet. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Particle and Google Meet to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Particle and Google Meet
Triggers and actions 1 trigger ยท 10 actions
Trigger
New device event (instant)Fires when a matching device event is published, delivered via a Particle webhook integration.
- Execute a logic function
Run a configured Particle Logic function and return its result.
- Get ledger instance
Retrieve the current data for a ledger instance (shared cloud/device key-value state).
- List devices
List all devices in your account or product fleet.
- Publish an event
Publish a custom event to the device cloud so other devices or integrations can subscribe to it.
- Set ledger instance data
Update the data stored in a ledger instance.
Action
Create MeetCreates a new google meet space, optionally configuring its access type and entry point access controls.
- Get Conference Record For Meet
Get conference record
- Get Meet
Retrieve details of a google meet space using its unique identifier.
- List Conference Records
Tool to list conference records. use when you need to retrieve a list of past conferences, optionally filtering them by criteria like meeting code, space name, or time range.
- Update Space
Updates a meeting space. use this tool to modify the settings of an existing google meet space. requires the space resource in the request body and the space name in the path.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.