# Zapier as a carrier for if.trace (if.bus preview one-pager)

**Audience:** preview cohort  
**Reality gate:** no Zapier adapter is deployed on this host; this is a roadmap integration for `if.api` + `if.bus`.

---

## 1) What Zapier is (black/white)

- Zapier is an automation platform that connects apps with triggers and actions.
- It orchestrates cross-app workflows and task execution.
- It does not, by itself, provide a receipt for your output bytes.

## 2) What if.trace is (black/white)

- `if.trace` binds bytes to hashes with receipts (signatures only when present and verifiable).
- `if.trace` proves integrity of specific output bytes, not correctness or truth.

## 3) Overlap (small)

- Both touch the same workflow outputs.
- Zapier routes or produces outputs; `if.trace` attests to the outputs you publish.

## 4) Non-overlap (important)

- Zapier does not provide cryptographic receipt chains for output artifacts.
- `if.trace` is not an automation platform or workflow engine.

## 5) Recommended pattern (carrier model)

1) Use Zapier to orchestrate the workflow and produce an output artifact.
2) Bind the output to `if.trace` receipts.
3) Store or share the receipt links alongside the Zapier task outcome.

## 6) What not to claim

- Do not claim "Zapier = receipt for output bytes".
- Do not claim "if.trace replaces Zapier automation".

---

## References (one URL per line)

https://docs.zapier.com/platform/home
https://docs.zapier.com/platform/docs
https://infrafabric.io/if/trace/
