Meeting Automation Configuration
Salesforce-side configuration after the Real Bots package is installed. The full step-by-step walkthrough lives in the Administrator Guide; this page is the configuration summary.
Order of operations
- Install the managed package — see Installation.
- Set up the Google Cloud project and OAuth client — see Google Meet Integration.
- Enter the Google client settings in Salesforce custom metadata.
- Assign the Meeting Automation permission sets.
- Schedule the processing job — see Processing & Salesforce Records.
- Connect a Google account and verify with a real meeting.
Salesforce settings
| Setting | Where | Notes |
|---|---|---|
| Google OAuth Client ID | Custom metadata | From the Google Cloud OAuth client |
| Google OAuth Client Secret | Custom metadata | Stored as a protected value |
| Redirect URI | Google Cloud console | Must match your My Domain URL |
| Remote Site / Named Credential | Setup | Allows the callouts to Google APIs |
| Processing schedule | Apex scheduled job | Controls how often meetings are picked up |
All Real Bots components are prefixed with the ribot namespace. When searching Setup, include the prefix.
Verification
Run a real meeting end to end and confirm a candidate task appears in the review dashboard. The Meeting Log is the first place to look when nothing appears — see Troubleshooting.
Was this helpful?
Last updated 1 month ago