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.

Awaiting approvalBuilt and submitted. Waiting for Zapier to approve it; it cannot be found in Zapier until then.

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.

1
Open your Zap and add a step at the end. Search for Locker by FlurryPORT and choose the Archive Run action.
2
Choose Sign in. A FlurryPORT window opens. Enter your email, then use the sign-in link or code we mail you.
3
Approve the connection. It can archive runs, read them back and see your account email, which Zapier uses to name the connection. It cannot reach anything else in your account.
4
Fill in What went in and What came out with data from the earlier steps of the Zap. Everything else is optional.
5
Test the step. You get a receipt back. Turn the Zap on and every run is archived from then on.
Put the step last. It only records what the earlier steps did, so if it ever fails, nothing your Zap already did is undone.

The Archive Run fields

FieldWhat to put in it
What went inThe data this run started from. Map fields from your trigger. Text or JSON.
What came outWhat the run produced. Map fields from the steps before this one. Text or JSON.
Run statusSuccess, Error or Unknown. Defaults to Success.
Run idYour 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 nameThe name shown for this Zap in your archive. You can rename it later in FlurryPORT.
Install nameGroups runs into one chain. Leave it blank and each Zap keeps its own chain, which is what most people want.
Started at, Finished atWhen the run began and ended. Finished at defaults to now.
LabelsUp to 20 name and value pairs, such as a client name, to find runs by later.

What the step gives back

FieldWhat it is
Receipt idThe id of this run in your archive.
Receipt pageA link to the public receipt. Send it to anyone who needs proof of the run.
Position in the chainWhere this run sits in its chain, counting from 1.
Receipt fingerprintThe SHA-256 fingerprint of the signed receipt.
Already archivedTrue when the run id was sent before and the first receipt came back.
Plan stateFree, paid or locked.
Free runs remainingHow 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 happenedWhat Zapier does
Too many runs at onceWaits, then retries the run by itself.
Your sign-in expiredRefreshes the connection and retries.
The step was given something it cannot archiveStops that one run with a message. The Zap stays on.
A run larger than 1 MBArchives 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.