Connect Fluent Support and Willo

Both apps 32Fluent Support 12Willo 20

• Trigger
  New Customer

  Triggers when a new customer is added in Fluent Support.

• Trigger
  New Ticket

  Triggers when a new support ticket is created in Fluent Support.

• Action
  Add Tag to Ticket

  Adds an existing tag to a Fluent Support ticket.

• Action
  Close Ticket

  Closes a Fluent Support ticket.

• Action
  Create Customer

  Creates a new customer in Fluent Support with their name, email, contact details and an optional note.

• Action
  Create Ticket

  Creates a new support ticket in Fluent Support for an existing customer.

• Action
  Get Ticket

  Returns a Fluent Support ticket with its customer, responses and details.

• Action
  List Customers

  Returns the customers in your Fluent Support help desk, optionally filtered by a search term.

• Action
  List Tickets

  Returns support tickets from Fluent Support, optionally matching a search term.

• Action
  Reopen Ticket

  Reopens a closed Fluent Support ticket.

• Action
  Reply to Ticket

  Adds an agent reply or internal note to a Fluent Support ticket, optionally closing the ticket.

• Action
  Update Ticket

  Updates one property of a ticket — its priority, customer priority, assigned agent or product.

• Trigger
  List Users

  Triggers when a new user is added to your Willo account.

• Action
  Accept Candidate

  Marks a participant in a Willo interview as Accepted and returns the updated participant. Can also update the participant's name, phone number and custom ID in the same step.

• Action
  Add department

  Creates a new department in your Willo organisation and returns the department, including its key and branding.

• Action
  Add interview from template

  Creates a new interview in Willo from one of your interview templates and returns the new interview.

• Action
  Create Company

  Creates a new company as a child organisation under your Willo organisation, with the owner you name.

• Action
  Create Interview

  Creates a new video interview in Willo with its questions, department, message templates and settings.

• Action
  Delete interview

  Deletes an interview from your Willo account.

• Action
  Delete participant

  Deletes a participant from Willo. Returns whether the deletion was confirmed.

• Action
  Get interview

  Returns a Willo interview by its key, including its questions, owner, department, reviewers, message templates and settings. An error occurs if the interview is not found.

• Action
  Get participant

  Returns a Willo participant (candidate) with their contact details, status, interview, department, scores and answers.

• Action
  Get user

  Returns a Willo user's details, including email, full name, phone, role and status.

• Action
  Invite Someone

  Invites a person to a Willo interview as a participant and returns the new participant with their invite link.

• Action
  List departments

  Returns the departments in your Willo organisation, optionally filtered by name, owner email or owner.

• Action
  List interviews

  Returns the interviews in your Willo account, optionally narrowed by department, owner or a search term, and sorted the way you choose.

• Action
  List message templates

  Returns the message templates (email and SMS) in your Willo account, optionally filtered by title, type or trigger.

• Action
  List participants

  Returns the participants in your Willo account, optionally narrowed to an interview, department or owner, or by a text search.

• Action
  List users

  Returns the users in your Willo account with their key, email and full name.

• Action
  Reject Candidate

  Rejects a candidate by setting the participant's status to Rejected, optionally updating their name, phone or custom ID.

• Action
  Update interview

  Updates an existing interview's details, questions, reviewers, message templates and settings, changing only the values you provide. Returns the updated interview.

• Action
  Update participant

  Updates a participant's name, phone, status (Accepted or Rejected) or your own reference ID.

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