Connect Uplup to Leexi

Both apps 38Uplup 18Leexi 20

• Trigger
  New Response

  Triggers when someone submits a response to a quiz or form in Uplup. Includes all answers, contact info, and quiz-specific data like score and result.

• Action
  Add field

  Add a new field to a form at an optional position.

• Action
  Add form

  Create a new form or quiz with optional fields, styling, and quiz settings.

• Action
  Add wheel

  Create a new spinning wheel with customizable entries, settings, and appearance.

• Action
  Add wheel entries

  Append one or more entries to a wheel without replacing the existing list.

• Action
  Delete field

  Remove a field from the form.

• Action
  Delete form

  Permanently delete a form and all associated data.

• Action
  Delete wheel

  Permanently delete a wheel and all its associated data including spin history.

• Action
  Get form

  Retrieve a single form with all its fields, pages, styling, and settings.

• Action
  Get wheel

  Retrieve detailed information about a specific wheel including all entries and settings.

• Action
  List fields

  Get all fields for a form, ordered by position.

• Action
  List forms

  Return a paginated list of all forms and quizzes in the account.

• Action
  List submissions

  Get paginated submissions for a form with optional filtering (limit, since).

• Action
  List wheels

  Retrieve a paginated list of all wheels belonging to the account.

• Action
  Spin wheel

  Programmatically spin a wheel and get a randomly selected winner; the spin is recorded to the wheel's results history.

• Action
  Update field

  Update field properties; only provided fields are modified.

• Action
  Update form

  Update form properties; only provided fields are modified.

• Action
  Update wheel

  Update an existing wheel's title, entries, settings, and appearance.

• Action
  Add meeting event

  Create a meeting event (schedule a meeting to be recorded).

• Action
  Add team

  Create a team in your Leexi workspace.

• Action
  Add user

  Creates a user in your Leexi workspace. Requires the write_users permission scope on the API key.

• Action
  Delete meeting event

  Deletes a Leexi meeting event. Requires the write_meeting_events permission scope on the API key.

• Action
  Delete team

  Delete a team of the workspace.

• Action
  Delete user

  Deactivates a Leexi user. Leexi never permanently deletes users: their calls and history are kept, sessions are revoked and they stop consuming a license. Deactivating an already inactive user still succeeds.

• Action
  Get call

  Get a single Leexi call or meeting, including its topics, AI summary prompts, tasks and transcript.

• Action
  Get call note

  Retrieve a single call note.

• Action
  Get meeting event

  Retrieve a single meeting event.

• Action
  Get team

  Retrieve a single team of the workspace.

• Action
  Get user

  Retrieve a single user of the workspace.

• Action
  Launch meeting assistant

  Sends the Leexi meeting assistant (bot) into a meeting event, or stops the bot that is already running.

• Action
  List call notes

  List call notes for a given call.

• Action
  List calls

  List the calls and meetings the API key can access, newest first by default, with optional filters on date, source, owner, participants, conversation type and customer contact.

• Action
  List teams

  List all teams in your Leexi workspace.

• Action
  List users

  List all users in your Leexi workspace.

• Action
  Request presigned recording upload URL

  Requests a presigned URL for uploading a call recording before creating the call with Add call. Requires the write_calls permission scope on the API key.

• Action
  Update call note

  Updates the translated text of a call note for one language. The original note text is not modified. Requires the write_calls permission on the API key.

• Action
  Update team

  Update the name or active status of a team in your Leexi workspace. Only the values you fill in are changed.

• Action
  Update user

  Updates a Leexi user. Only the fields you fill in are changed.

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