Connect Formstack to Luma

Both apps 36Formstack 19Luma 17

• Trigger
  New Form

  Triggers when a new form is created in the account.

• Action
  Copy Form

  Create a copy of an existing form.

• Action
  Create Folder

  Create a new form folder.

• Action
  Create Form

  Create a new form.

• Action
  Create Form Field

  Add a new field to a form.

• Action
  Create Submission

  Submit data to a form. Field values are passed as field_<id> keys.

• Action
  Create Webhook

  Create a webhook on a form that POSTs to a URL when a submission is received.

• Action
  Delete folder

  Delete a folder.

• Action
  Delete Form

  Delete a form by ID.

• Action
  Delete Submission

  Delete a submission by ID.

• Action
  Delete Webhook

  Delete a webhook by ID.

• Action
  Get folder

  Get a folder by id.

• Action
  Get Form

  Retrieve details for a single form by ID.

• Action
  Get form field

  Get one field on a form.

• Action
  List Form Confirmations

  List confirmation emails configured on a form.

• Action
  List Form Fields

  List all fields on a form.

• Action
  List form notifications

  List notification emails for a form.

• Action
  List Webhooks

  List webhooks configured on a form.

• Action
  Update folder

  Update a folder.

• Action
  Add guests

  Adds one or more guests to a Luma event, optionally assigning ticket types, an approval status, and whether Luma emails them. Returns any guests Luma skipped.

• Action
  Add host

  Adds a host to a Luma event, as a manager or as check-in staff, by email address.

• Action
  Add ticket type

  Creates a new ticket type (free or paid) for a Luma event. Paid ticket types require the calendar to have a connected Stripe account.

• Action
  Apply contact tag

  Applies a contact tag to existing contacts on your Luma calendar, identified by user ID or email. Does not create new contacts.

• Action
  Block contact

  Blocks a contact on your Luma calendar so they can't follow it or join its events, and stop receiving your invites and newsletters.

• Action
  Cancel event

  Cancels a Luma event. The event is permanently deleted, all guests are notified, and paid guests can optionally be refunded.

• Action
  Create Calendar Person

  Adds a person to your Luma calendar as a contact by email, optionally with a name and contact tags, so you can invite them to events and send newsletters.

• Action
  Get calendar

  Returns the details of the Luma calendar your connected API key belongs to, including its name, URL, location, social handles and default event settings.

• Action
  Get event

  Returns the details of a Luma event, including its schedule, location, visibility, hosts and, for events you manage, guest counts by status.

• Action
  Get guest

  Returns one guest of a Luma event, looked up by guest ID, ticket key, guest key or email, including their approval status, registration answers and tickets.

• Action
  Import contacts

  Imports contacts into your Luma calendar so you can invite them to events and send them newsletters, optionally tagging them.

• Action
  List contacts

  Returns the contacts (people) on your Luma calendar, optionally filtered by a name/email search, tags or membership status.

• Action
  List events

  Returns the events on your Luma calendar, optionally filtered by date range, submission status, platform and access level.

• Action
  List guests

  Returns the guests who have registered for or been invited to a Luma event, with their approval status, contact details, registration answers and tickets.

• Action
  List ticket types

  Returns every ticket type set up for a Luma event, including its name, price and capacity.

• Action
  Send invites

  Sends people an email invite (and an SMS if their phone is linked to Luma) to a Luma event. Returns any invitees who were skipped because they unsubscribed, were removed, or are blocked.

• Action
  Update guest status

  Changes a guest's registration status for a Luma event — approve (Going), decline, move back to pending approval, or waitlist — optionally refunding a paid guest and adding a personal note to the notification email.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.