Connect UpKeep to Luma

Both apps 50UpKeep 33Luma 17

• Trigger
  New Purchase Order

  Triggers when a new purchase order is created.

• Trigger
  New Work Order

  Triggers when a new work order is created.

• Action
  Add Asset

  Create a new asset.

• Action
  Add Location

  Creates a new location in UpKeep.

• Action
  Add User

  Creates a new user in your UpKeep account.

• Action
  Add Vendor

  Create a new vendor.

• Action
  Create Purchase Order

  Creates a purchase order in UpKeep.

• Action
  Create Work Order

  Creates new work order.

• Action
  Delete Purchase Order

  Deletes a specific purchase order in UpKeep.

• Action
  Delete Work Order

  Deletes a specific work order in UpKeep.

• Action
  Find Asset

  Finds assets matching the given name, barcode, serial number, location, status, category or other criteria. Returns the first match plus the list of all matches on the first page of results.

• Action
  Find Location

  Returns the locations whose name matches the name you supply, optionally narrowed by parent location, creator, hierarchy level, custom field and created/updated dates.

• Action
  Find Part

  Finds parts in UpKeep by name.

• Action
  Find Vendor

  Returns the vendors whose business name matches the one supplied, with the first match broken out.

• Action
  Get Asset

  Gets a specific UpKeep asset by its ID, including its custom field values.

• Action
  Get Location

  Gets a specific UpKeep location by its ID.

• Action
  Get Part

  Gets a specific part from the UpKeep inventory by its ID.

• Action
  Get Purchase Order

  Gets a specific purchase order by its ID.

• Action
  Get User

  Gets a specific UpKeep user by ID.

• Action
  Get Vendor

  Gets a specific vendor by its ID.

• Action
  Get Work Order

  Retrieve a single work order by ID.

• Action
  List Assets

  Lists the assets in your UpKeep account, optionally filtered by name, barcode, serial number, location, status, category, assigned or creating user, downtime status, one custom field, and created/updated time ranges.

• Action
  List Locations

  Lists the locations in your UpKeep account, optionally filtered by name, creator, parent location, hierarchy level, custom field or created/updated date.

• Action
  List Purchase Orders

  Lists purchase orders in the UpKeep account, optionally filtered by status.

• Action
  List Vendors

  List/page all vendors.

• Action
  List Work Orders

  List/page all work orders with filters.

• Action
  Update Asset

  Updates the fields you supply on an existing UpKeep asset. Fields left blank are not changed.

• Action
  Update Location

  Updates an existing location in UpKeep. Only the fields you fill in are changed.

• Action
  Update Part

  Updates an existing part in UpKeep. Only the fields you fill in are changed.

• Action
  Update Purchase Order

  Updates an existing purchase order in UpKeep. Only the fields you fill in are changed.

• Action
  Update User

  Updates an existing UpKeep user. Only the fields you fill in are changed; blank fields are left as they are.

• Action
  Update Vendor

  Update fields on an existing vendor.

• Action
  Update Work Order

  Update fields on an existing work order.

• 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.