Update Guest Status approves, declines or waitlists a Luma event guest. It runs on your own Luma account.
Before you start
Account: your own Luma account. Nothing is charged from your wallet. Connect it first (steps below).
Input: the row needs the guest's ID.
Important: Update Guest Status writes outside Loopster. With Auto-run on, new values in the first column trigger the row workflow, so data can be sent without you clicking run. Add the column without running it and test one row first. See Run columns safely: Auto-run, test one row, then run the rest.
How do I connect Luma?
Open Settings, then Connections.
Click Create.
In the Connect an account window, find Luma in the list and click it.
Follow the steps that open for Luma.
Then open the column's settings: the Account block shows which account the column uses, with a Manage accounts link. See Connections: Loopster-provided accounts and your own.
How do I use Update Guest Status?
Click Add column, then Add enrichment.
Open the Export tab. Under Events, click Update Guest Status (Luma).
Map the guest's ID, and set the status to apply (approve, decline or waitlist). The settings also include an event ID.
Click the arrow next to the main button and choose Add column without running.
Click the play button on one row, then double-click the cell to read the result.
Check the result in Luma too.
To run the rest, click the play button on the column header and choose Run all N empty rows in the Run column dialog.
How do I check it worked?
Double-click a cell.
The details show the fields of the result. Hover a field and click Add to column to put it in its own column. See Put a result's fields into their own columns.
Also check the result in Luma.
Troubleshooting
Quick answer
Auto-run is off, or the column was added without running.
A required input or setting has no value (the panel footer warns).
The cell says Error: open it and read the message. Then check the Luma connection under Settings, then Connections.
Nothing happens, or the cells stay empty
What you see: The column exists, but no row has run.
Why it happens: Auto-run is Off (the app says "New rows and values will not run on their own"), or you chose Add column without running.
What to do: Click a row's play button, or use the column header's Run column dialog. See Why didn't my column run?.
The footer says "Select a column for … before running"
What you see: A warning such as "Select a column for … before running." in the panel footer.
Why it happens: A required input or setting (marked with *) has no value. An input can be empty even when a suggestion names a column.
What to do: Click the input, press / and pick a column from the list. Do not close the list with Esc: a / or @ is then left in the field as plain text.
My cells say Skipped
What you see: Skipped in the cells.
Why it happens: Skipped means "Did not run because of filters or missing dependencies."
What to do: Double-click the cell and read the message. Check that every input is mapped to a column, and look under Run Settings for Add run condition ("Only run if this formula resolves to true.").
My cells say Unsatisfied
What you see: Unsatisfied in the cells.
Why it happens: Unsatisfied means "Enrichment ran correctly, but output didn't match expected format."
What to do: Double-click the cell and read the message. Check the input values in that row, and test one row before you re-run many. See What a cell's message means.
A cell says Error
What you see: The cell says Error, and the footer shows a count such as "1 cell failed".
Why it happens: Error means "Crashed, something went wrong." The message is in the cell it happened in.
What to do: Double-click the cell and read the message. Then open Settings, then Connections, and check the Status of the Luma connection. Check Luma before you re-run, because a re-run runs the action again.
I am not sure which Luma account a column uses
What you see: You want to know which Luma account a column runs on.
Why it happens: Luma runs on your own account, and the column's Account block shows which account it uses.
What to do: Open the column's settings and look at the Account block. Its Manage accounts link is next to it. Settings, then Connections, lists every account the workspace can run on. If Luma is not there, click Create and find Luma in the list.
The result did not change after I edited an input
What you see: A finished cell keeps its old result after you change an input.
Why it happens: With Auto-run on, Keep existing results is ticked: "Only errored, empty and new cells run. A completed answer is left alone even when one of its inputs changes."
What to do: Double-click the cell and click Re-run this cell, or click the play button on the column header and choose Overwrite all N rows in the Run column dialog. Read the line under each option first. Either one runs the action on Luma again.
Luma got the same data twice
What you see: Repeated changes or duplicate entries in Luma.
Why it happens: This action writes outside Loopster. Re-run this cell and Overwrite all N rows run it again, so Luma may receive the data again.
What to do: Test one row first and check it in Luma. Keep Auto-run off until the first row looks right.
What does it cost?
Luma runs on your own account. Nothing is charged from your wallet. See Your wallet and keeping spend under control.
Good to know
Update Guest Status is the only Luma action in Loopster. It is in the Export tab, under Events.
It is not marked as eligible for a waterfall step.
It does not create rows in your table.
It writes outside Loopster.