Connect Debitura to Uplup

Both apps 30Debitura 12Uplup 18

• Trigger
  New Case

  Triggers when a new collection case appears in your Debitura account.

• Action
  Add Case Message

  Posts a message on a Debitura collection case, visible to you and the assigned collection partner, who is emailed about it.

• Action
  Check Collection Eligibility

  Checks whether a debt can be collected in the debtor's country, and tells you which collection partner would take the case.

• Action
  Create Case

  Opens a debt collection case in Debitura for a debtor you specify, with either a total owed or the unpaid invoices behind it.

• Action
  Find Case

  Looks up a single debt collection case in Debitura by its case reference, your own reference, or its id, and returns the case.

• Action
  Find Payment

  Finds one payment recorded on a Debitura case, by the payment's id, and returns it.

• Action
  Get Case Files

  Returns the documents attached to a collection case.

• Action
  Get Case Messages

  Returns the messages posted on a Debitura collection case, in the order they were sent.

• Action
  Get Case Timeline

  Returns everything that has happened on a collection case, in order, plus the stage the case has reached.

• Action
  Get Contract Status

  Returns whether the agreements needed to collect on a case have been signed yet.

• Action
  Preview Case

  Checks a debt before you file it: whether Debitura can collect it, which collection partner would take it, what it would cost, and any agreements you would need to sign. No case is created.

• Action
  Upload File to Case

  Attach a document to a collection case, such as an invoice, contract, or correspondence. Supporting documents help the collection partner resolve the case faster.

• 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. POST /api/v1/forms/{form_id}/fields.

• Action
  Add form

  Create a new form or quiz with optional fields, styling, and quiz settings. POST /api/v1/forms.

• Action
  Add wheel

  Create a new spinning wheel with customizable entries, settings, and appearance. POST /api/v1/wheels.

• Action
  Add wheel entries

  Append one or more entries to a wheel without replacing the existing list. POST /api/v1/wheels/{wheel_id}/entries.

• Action
  Delete field

  Remove a field from the form. DELETE /api/v1/forms/{form_id}/fields/{field_id}.

• Action
  Delete form

  Permanently delete a form and all associated data. DELETE /api/v1/forms/{form_id}.

• Action
  Delete wheel

  Permanently delete a wheel and all its associated data including spin history. DELETE /api/v1/wheels/{wheel_id}.

• Action
  Get form

  Retrieve a single form with all its fields, pages, styling, and settings. GET /api/v1/forms/{form_id}.

• Action
  Get wheel

  Retrieve detailed information about a specific wheel including all entries and settings. GET /api/v1/wheels/{wheel_id}.

• Action
  List fields

  Get all fields for a form, ordered by position. GET /api/v1/forms/{form_id}/fields.

• Action
  List forms

  Return a paginated list of all forms and quizzes in the account. GET /api/v1/forms.

• Action
  List submissions

  Get paginated submissions for a form with optional filtering (limit, since). GET /api/v1/forms/{form_id}/submissions.

• Action
  List wheels

  Retrieve a paginated list of all wheels belonging to the account. GET /api/v1/wheels.

• Action
  Spin wheel

  Programmatically spin a wheel and get a randomly selected winner; the spin is recorded to the wheel's results history. POST /api/v1/wheels/{wheel_id}/spin.

• Action
  Update field

  Update field properties; only provided fields are modified. PATCH /api/v1/forms/{form_id}/fields/{field_id}.

• Action
  Update form

  Update form properties; only provided fields are modified. PATCH /api/v1/forms/{form_id}.

• Action
  Update wheel

  Update an existing wheel's title, entries, settings, and appearance. PUT /api/v1/wheels/{wheel_id}.

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