← Rize + Loom integration

Scheduled routine

Loom MCP: Review Recorded Meeting Time with Rize

Check accessible Loom recording context against Rize time entries.

A meeting-time review with proposed corrections and source references.

How to set it up

1

In Rize, open Settings → Integrations and select the MCP filter. Find Loom, connect with your own account and approve access. Available tools depend on your account and connector permissions.

2

Open Routines, create a routine, and select Loom as a connector. Paste the example prompt below and specify the clients, projects and date range you want reviewed.

3

Choose a daily or weekly schedule and your preferred run time. Save and enable the routine. You can also run it manually to check the first result.

4

Review the finished brief in Rize. Check source matches and missing context before making changes. These example prompts request read-only reviews, not unattended writes.

What should your routine ask?

This prompt requests a read-only review. Replace the date range and project scope before you save it.

Use the Loom connector to read available recording metadata and any text it exposes from this week. Compare with search_my_meetings and list_my_time_entries in Rize. Flag recordings with a clear meeting match but no matching time entry. Propose entries only when dates and durations are supported; never infer working time from recording length. Do not create entries.

Connector tools are discovered when the routine runs. Access depends on your connected account. Routines use AI credits.

Frequently Asked Questions

Open Settings → Integrations, select the MCP filter, and connect Loom. Then select it in your routine. The routine can use only the connected tools your account permits.

No. This example prompt asks for a review brief without record changes. Routines can run write tools where supported, so review any prompt changes before enabling a schedule.

Check the connection and account permissions, then narrow the prompt to information the connector exposes. Missing context should be flagged in the brief, not filled in with guesses. Scheduled runs use AI credits.

Need help with this integration? Contact support