Locker on Make

Add one module to a scenario and every run is kept in Locker, exactly as it happened, with a signed receipt anyone can check.

By install linkWorks today through an install link. Waiting for Make to approve it for the app list.

Before you start

You need a Make account 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 code. Locker starts free with 250 runs or 14 days, whichever comes first.

Install the app

Locker by FlurryPORT is installed from a link. It is not in the app list inside Make yet, so searching for it there finds nothing until you install it. Install Locker by FlurryPORT in Make.

Add Locker to a scenario

1
Open the install link while signed in to Make and choose Install.
2
Open your scenario and add a module. Search for Locker by FlurryPORT and choose Archive a run.
3
Choose Add next to Connection. A FlurryPORT window opens. Choose Continue, enter your email, then enter the 6-digit code we mail you in the same window. A new email address gets a new account and is asked to accept the terms.
4
Choose Authorize. The connection can archive runs, read them back and see your account email, which Make uses to name the connection. It cannot reach anything else in your account.
5
Fill in What went in and What came out with data from the earlier modules of the scenario. Everything else is optional.
6
Choose Run once. You get a receipt back. Turn the scenario on and every run is archived from then on.
Put the module where the result of the run is known, usually last. It only records what the earlier modules did, so if it fails, nothing your scenario already did is undone.

The Archive a run fields

FieldWhat to put in it
Install nameGroups runs into one chain. Leave it empty and the scenario name is used, so each named scenario keeps its own chain.
Scenario nameThe name shown for this scenario in your archive. Fill it in: with both names empty, every scenario shares one chain named Make.
Run IDYour own ID for the run, such as an order number. Leave it empty and Locker names the run. The same ID with the same data returns the first receipt and archives nothing new. The same ID with different data is refused.
Run statusSuccess, Error or Unknown. Defaults to Success.
What went inThe data this run started from. Map it from an earlier module, or type a value.
What came outWhat the run produced. Map it from the modules before this one.
LabelsName and value pairs, such as a client name, to find runs by later.

What the module 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.
Previous fingerprintThe fingerprint of the receipt before this one. Empty for the first run in a chain.
Install IDThe ID of the chain the run went into.
Signed receipt (JSON)The receipt itself.
Stored bytesThe size of what was archived.
Already archivedYes when the Run ID was sent before with the same data and the first receipt came back.
Plan stateYour plan, the free runs remaining and a link to the plan page.

Use these in later modules if you add any. A common one is to write the receipt page link into the spreadsheet row or ticket the scenario just created.

The other two modules

ModuleWhat it does
Get a receiptReturns one archived run and its signed receipt. Give it the Receipt ID that Archive a run returned.
Make an API callSends a request to the Locker API through your connection, for anything the other two do not cover. Enter a path such as /api/v1/locker/installs, which lists your installs.

If something goes wrong

What happenedWhat you see
Too many runs at onceThe module reports a rate limit and Make pauses the scenario for a while. Run it again later.
A Run ID was used before with different dataThat run stops with a message naming the first receipt. Use a new Run ID for a new run, or leave Run ID empty.
A run larger than 1 MBThat run stops with a message. Archive the fields that matter in place of a whole file.

Where your runs are

Sign in to FlurryPORT with the same email and open Locker. Each chain appears as its own install, under the scenario name you gave it. The Locker page covers reading the archive, the receipt page, how long runs are kept, and the API the module calls.