Connect Grain to Crush
Give Crush governed access to Grain’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Grain to Crush in four steps
Admins approve the server once. Everyone in Crush then gets it through the same governed connection.
- 1
Approve Grain in Runlayer
Add Grain from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Crush to Runlayer
Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches Grain’s 15 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Crush setup guide - 3
Sign in to Grain
Sign in the way Grain requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Grain from Crush
Grain’s approved tools appear in Crush. Every call is checked against policy and recorded.
Tools
15 Grain tools in Crush
Runlayer policy decides which of these Crush users can call. 15 read data only.
Myself
Get information about the logged-in Grain user.
List meetings
Returns a filtered list of Grain meetings you have access to, ordered by most recent.
List attended meetings
Returns a filtered list of Grain meetings you have attended, ordered by most recent.
Fetch meeting
Fetches information about a single Grain meeting by ID.
Fetch meeting notes
Fetches the AI notes payload from a single Grain meeting by ID.
Fetch meeting transcript
Fetches the transcript from a single Grain meeting by ID.
Search persons
Returns a filtered list of persons that were participants of Grain meetings you have access to.
Search companies
Returns a filtered list of companies that were participants of Grain meetings you have access to.
Control
What Runlayer can see and stop in Crush
Some controls apply to every client at the gateway. Others depend on what Crush exposes to Runlayer.
Gateway policy (available)
Every Grain call from Crush passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Crush as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Crush yet, so control happens at the gateway.
Frequently asked questions
Connect more
