Locker on Zapier
Add one step to the end of a Zap and every run is kept in Locker, exactly as it happened, with a signed receipt anyone can check.
Before you start
You need a Zap and an email address. The connection step creates your FlurryPORT account if you do not have one. There is no password: we mail you a sign-in link or a code. Locker starts free with 250 runs or 14 days, whichever comes first.
Add Locker to a Zap
These are the steps once Zapier approves the app. Until then, a search for Locker by FlurryPORT in Zapier finds nothing. The Locker page lists the ways in that work today.
The Archive Run fields
| Field | What to put in it |
|---|---|
| What went in | The data this run started from. Map fields from your trigger. Text or JSON. |
| What came out | What the run produced. Map fields from the steps before this one. Text or JSON. |
| Run status | Success, Error or Unknown. Defaults to Success. |
| Run id | Your own id for the run, such as an order number. Leave it blank and Locker names the run. Sending the same id twice returns the first receipt and archives nothing new. |
| Workflow name | The name shown for this Zap in your archive. You can rename it later in FlurryPORT. |
| Install name | Groups runs into one chain. Leave it blank and each Zap keeps its own chain, which is what most people want. |
| Started at, Finished at | When the run began and ended. Finished at defaults to now. |
| Labels | Up to 20 name and value pairs, such as a client name, to find runs by later. |
What the step gives back
| Field | What it is |
|---|---|
| Receipt id | The id of this run in your archive. |
| Receipt page | A link to the public receipt. Send it to anyone who needs proof of the run. |
| Position in the chain | Where this run sits in its chain, counting from 1. |
| Receipt fingerprint | The SHA-256 fingerprint of the signed receipt. |
| Already archived | True when the run id was sent before and the first receipt came back. |
| Plan state | Free, paid or locked. |
| Free runs remaining | How much of the free allowance is left. |
Use these in later steps if you add any. A common one is to write the receipt page link into the spreadsheet row or ticket the Zap just created.
If something goes wrong
The step is built so that a problem on our side never turns your Zap off.
| What happened | What Zapier does |
|---|---|
| Too many runs at once | Waits, then retries the run by itself. |
| Your sign-in expired | Refreshes the connection and retries. |
| The step was given something it cannot archive | Stops that one run with a message. The Zap stays on. |
| A run larger than 1 MB | Archives a fingerprint of the oversized part in place of the part. The run gets its receipt. |
Where your runs are
Sign in to FlurryPORT and open Locker. Each Zap appears as its own install, under the workflow name you gave it. The Locker page covers reading the archive, the receipt page, how long runs are kept, and the API the step calls.