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.
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
The Archive a run fields
| Field | What to put in it |
|---|---|
| Install name | Groups runs into one chain. Leave it empty and the scenario name is used, so each named scenario keeps its own chain. |
| Scenario name | The name shown for this scenario in your archive. Fill it in: with both names empty, every scenario shares one chain named Make. |
| Run ID | Your 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 status | Success, Error or Unknown. Defaults to Success. |
| What went in | The data this run started from. Map it from an earlier module, or type a value. |
| What came out | What the run produced. Map it from the modules before this one. |
| Labels | Name and value pairs, such as a client name, to find runs by later. |
What the module 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. |
| Previous fingerprint | The fingerprint of the receipt before this one. Empty for the first run in a chain. |
| Install ID | The ID of the chain the run went into. |
| Signed receipt (JSON) | The receipt itself. |
| Stored bytes | The size of what was archived. |
| Already archived | Yes when the Run ID was sent before with the same data and the first receipt came back. |
| Plan state | Your 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
| Module | What it does |
|---|---|
| Get a receipt | Returns one archived run and its signed receipt. Give it the Receipt ID that Archive a run returned. |
| Make an API call | Sends 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 happened | What you see |
|---|---|
| Too many runs at once | The 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 data | That 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 MB | That 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.