Ironfang integration researchA little less busywork with Ironfang.
Research only. Grunt is prelaunch, live service is paused, and live provider connections and outcomes remain unverified. The operations and examples below are not confirmed live Grunt features or approved supplier commitments.
Explore possible Ironfang workflows with Grunt. Documented operations include Audit: Archive a monitor (one-way; its audits and evidence remain); Audit: Apply one decision to several findings; Audit: What changed against the observation before it. Actions on this page are research candidates from public integration definitions, not confirmation that Grunt support is live.
Exploratory scope only: these candidates come from public integration definitions and are not confirmed as live Grunt features.
Ironfang
“Explore whether a Grunt integration could archive a monitor (one-way; its audits and evidence remain), then apply one decision to several findings in Ironfang. Show me the result and wait for my approval before changing anything.”
Illustrative steps and outcome; no real work is performed here.
- 01Audit: Archive a monitor (one-way; its audits and evidence remain)
- 02Audit: Apply one decision to several findings
- 03Review the result before anything changes
A clearer next step, with the final say still yours.
Explore possibilities with Ironfang.
Researched operations, not a list of enabled Grunt actions. Actual support, account permissions, supplier terms, and live acceptance require separate verification.
162 researched capabilities across 5 groups
- Archive a monitor (one-way; its audits and evidence remain)
- Apply one decision to several findings
- What changed against the observation before it
- Create an encrypted S3/S3-compatible destination
- Create a monitor
- Create a deterministic rule
- Create a site
- Create a signed webhook endpoint
- Retire an endpoint (soft; its delivery history is kept)
- Disable a rule for future audits
- Stream an authenticated raw artifact
- Download the independently verifiable evidence ZIP
- Enable a rule for future audits
- Queue a manual S3 export
- Get audit lifecycle, compliance and integrity state
- Get one finding
- The numbers at the top of the finding inbox
- Get a monitor with its URL set
- One observation with its artifacts and rule results
- Get the active revision of a rule
- Get a site
- Read one organisation-owned delivery
- Tenant-scoped setup facts and recent activity for the portal
- Install a rule pack
- Page organisation webhook deliveries
- Page observations of an audit
- List organisation audits
- The organisation's recent product events, newest first
- List S3 destinations
- List export jobs
- The append-only history of a finding
- The finding inbox
- Packs installed on this site
- The monitor's audits, newest first
- List monitors
- A page's observation history, newest first
- The rule pack catalogue
- List every revision of a rule, newest first
- List site audits
- List the site's monitors
- List the site's versioned deterministic rules
- List sites
- List endpoint deliveries
- List lifecycle webhook endpoints
- Pause scheduling
- Replace a url_set monitor's URL list
- Resume scheduling
- Retire a rule
- Re-queue a failed delivery
- Replace the endpoint's signing secret
- Queue an audit now with the monitor's scope frozen as the scheduler would freeze it
- Trigger an asynchronous audit
- Upload and verify a connection-test object
- Send a signed endpoint.test event
- Uninstall a pack
- Assign, schedule, acknowledge, accept the risk, or close a finding
- Change a monitor's name, cadence, anchor, timezone, capture profile or change policy
- Revise a rule
- Enable or disable an endpoint, or change its subscribed events
- Upgrade an installed pack, or change its values
- Credits, quota position, projection and hosted evidence
Proposed setup considerations
The research notes below describe a possible setup. They are not instructions for an available Grunt connection; actual steps depend on supported operations and provider approval.
- 01
Start with a small, useful task.
Describe a routine step involving Ironfang. Keep a first version easy to review and change.
- 02
Plan the account access.
Check which Ironfang account, data, and permissions a safe connection would need. Start with the least access that can do the job.
- 03
Test the details together.
Validate a sample against a disposable account. Confirm which records are read, what could change, and how errors or duplicates are handled.
- 04
Keep the say-so.
Decide which steps could run on their own and which would need your review. Expand access only when the workflow needs it.
RESEARCH NOTES
Questions about the concept.
These notes describe possible uses. Customer availability remains unverified.
What could a Grunt integration do with Ironfang?
The documented operations include Audit: Archive a monitor (one-way; its audits and evidence remain); Audit: Apply one decision to several findings; Audit: What changed against the observation before it; Audit: Create an encrypted S3/S3-compatible destination. These are research candidates from public integration definitions and need validation and Grunt implementation before they can be treated as supported capabilities.
Could I keep a workflow read-only?
The research candidates do not confirm an implemented Ironfang connection or a read-only access mode. If built, verify least-privilege scopes and reject writes at the app API boundary.
Will every action run automatically?
If a connection is built, choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.
Do I need to review actions in Ironfang?
A future integration should let you decide which work could run on its own and which steps need your review.
A little less busywork.
A little more you.
Read the current prelaunch status and confirmed prices.
View pricing status Explore the simulation