Connect AirOps to Crush
Give Crush governed access to AirOps’s 100 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add AirOps to Crush in four steps
Admins approve the server once. Everyone in Crush then gets it through the same governed connection.
- 1
Approve AirOps in Runlayer
Add AirOps 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 AirOps’s 100 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Crush setup guide - 3
Sign in to AirOps
Sign in the way AirOps requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use AirOps from Crush
AirOps’s approved tools appear in Crush. Every call is checked against policy and recorded.
Tools
100 AirOps tools in Crush
Runlayer policy decides which of these Crush users can call.
Accept opportunity
Accept pending opportunities for a campaign and add them to the campaign action grid.
Add AEO region
Add a region (ISO alpha-2 country code) to a Brand Kit's configured AEO regions.
Add grid column
Add a new column to a grid table.
Analytics chart
Query analytics data and display it as an interactive chart.
Automated feedback report
AirOps only feedback tool.
Bulk update AEO prompt tags
Apply a single tag operation (add or remove) to a batch of AEO prompts in one Brand Kit, atomically.
Bulk update AEO prompt topics
Reassign a batch of AEO prompts to an existing topic in one Brand Kit.
Commit AEO prompt assignments
Commit the current prompt-assignment draft for a Brand Kit to live.
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 AirOps 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