How to Use Red Hat security advisory in Zapier
Fetch the products, component versions, and CVEs covered by a Red Hat advisory. Use it when you have an erratum and need to explain what that update fixes.
Prompts to try with Red Hat security advisory in Zapier
Copy an example into Zapier, or ask in your own words.
Recheck Red Hat security advisory for https://access.redhat.com/errata/RHSA-2021:5137 weekly. Report changes to its covered products, component versions, or CVE list.
Every Monday at 9am: use Red Hat security advisory to look this up and give me the result as a table.
Pull the latest numbers from Red Hat security advisory and tell me what changed since last week.
Check Red Hat security advisory and summarize what you find in three bullet points.
Pull the newest data from Red Hat security advisory and give me the result as a table.
How to set up Red Hat security advisory in Zapier
Pick the way that suits you. Each takes about two minutes.
Use the Spiral skill
- Send Zapier this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use Spiral's MCP server
- Add an MCP Client connection
In Zapier open Apps, click Add connection and search for MCP Client. Fill in the form:
https://api.spiral.ai/mcp
- Sign in to Spiral and approve
Spiral opens: sign in, pick the organization and click Authorize. No API key. Spiral gives the connection its own key; Zapier never sees it, and you can remove it under Settings › Connected apps in the console.
- Run a Spiral tool in a Zap
Add an MCP Client step to a Zap and choose the Run Tool action with your Spiral connection. Pick a tool: discover finds the right model for a task, estimate_cost prices it and run runs it. For example, run with:
{ "provider": "fal", "model": "fal-ai/flux/schnell", "input": { "prompt": "a lighthouse at dawn" }, "wait": true } - Run Red Hat security advisory in a workflow step
Give the step an instruction like the ones below and run it on your trigger or schedule. Spiral finds Red Hat security advisory, prices it and runs it each time the step fires.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run Red Hat security advisory
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "access-redhat-com/vulnerabilities/advisory", "input": { "advisory_id": "<advisory_id>" } }'
Then paste one of the prompts above: Zapier finds Red Hat security advisory on Spiral, shows the price and runs it.
Red Hat security advisory providers and prices
Spiral runs Red Hat security advisory through Alexandria. Open a card for today's price, with every fee included.
What can you do with Red Hat security advisory in Zapier?
Maintain a Red Hat vulnerability watchlist that highlights newly found records and changes in reported fix status. A scheduled agent can compare successive searches or record lookups and prepare a focused maintenance digest.
Prepare an incident brief
Find relevant package CVEs, inspect their reported product status, and summarize the advisories that deliver fixes for an incident review.
Plan a maintenance window
Build a product-specific vulnerability list and connect the findings to fixing advisories. Group the reported fixes into a maintenance review.
Investigate a scanner finding
Compare a reported CVE with Red Hat's product assessment and the relevant advisory. Identify the vendor evidence needed for a remediation decision.
Write remediation tickets
Turn package search results into tickets containing the CVE, Red Hat severity, reported product status, and fixing advisory where available.
Review a security update
Start with an advisory, list the vulnerabilities it addresses, and inspect the CVE assessments to explain the update's security purpose.
Document patch evidence
Assemble the advisory's covered products and component versions with the corresponding CVE assessments for a patch review record.
Count vulnerabilities and updates separately
Use matching CVEs and their advisory references to produce separate counts of vulnerabilities and fixing updates. Explain where one advisory addresses several CVEs.
More on Red Hat security advisory and Zapier
Overview
Red Hat security advisory in other agents
Questions about Red Hat security advisory in Zapier
Can Zapier use Red Hat security advisory?
Yes. Add Spiral to Zapier as an MCP server, and Zapier can find and run Red Hat security advisory like any built-in tool.
How much does Red Hat security advisory cost in Zapier?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Zapier plan is separate.
Do I need an Alexandria account to use Red Hat security advisory in Zapier?
No. Spiral runs Red Hat security advisory on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up Red Hat security advisory in Zapier?
About two minutes: add an MCP Client connection, then sign in to Spiral and approve, then run a Spiral tool in a Zap.
Does Zapier wait while Red Hat security advisory runs?
Red Hat security advisory runs in the background. Zapier starts the run, checks on it and gives you the json when it's ready.
Does this cover vulnerabilities from every software vendor?
The scope is Red Hat's product portfolio. Red Hat documents queries for any Red Hat product, including products beyond RHEL.
When does Red Hat publish vulnerability information?
Red Hat says it publishes CVE information and scores immediately after assessing disclosed or coordinated vulnerabilities, unless they are under embargo. It also updates machine-readable security data when fixes are released.
Does a CVE record always include a fixed package version?
No. Red Hat documents fixed package information as optional in a CVE record, including cases where multiple source RPMs share an erratum.
Can one advisory cover several vulnerabilities?
Yes. Red Hat advisories can address multiple CVEs, so counting advisories does not give you the number of vulnerabilities fixed.
Does a product-status review include fixes already released?
Yes, but Red Hat separates unresolved package states from releases that delivered fixes. Both are needed to describe the complete reported status of a CVE across products.
Start using Red Hat security advisory in Zapier
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Zapier:
set up https://spiral.ai/SKILL.md


