# AI Access Request Risk Review with Pipedream + Jodoo

## Use Case

Access requests need risk context, approval evidence, and a time-boxed owner before IT grants privileges.

## Workflow Pattern

1. HTTP trigger receives the source request or payload.
2. Pipedream prepares a structured access request decision.
3. API request step sends the mapped output to the Jodoo writeback endpoint.
4. Jodoo stores the operational record for queue review, ownership, and follow-up.

## Proof Record

- Jodoo data ID: `6a270500416604628a2ba26d`
- Record anchor: `Finance analytics workspace`
- Jodoo app: Access Request Risk Review

## What Jodoo Keeps

Jodoo stores requester, department, access type, resource, access level, review outcome, owner, and follow-up notes.

## How to Adapt

- Start with a synthetic sample, then replace it with your own intake source.
- Keep the Pipedream trigger and action names visible so the workflow is easy to rebuild.
- Keep the Jodoo fields specific to the review queue your team will actually use.