Connect Adyen and Halo Service Solutions

Both apps 28Adyen 12Halo Service Solutions 16

• Trigger
  New payment authorisation

  Webhook AUTHORISATION: result of authorisation request.

• Trigger
  New refund

  Webhook REFUND: result of refund request.

• Action
  Add payment

  Starts a payment (authorisation) in Adyen Checkout for the given amount, payment method and merchant account, and returns the payment's PSP reference and result code.

• Action
  Add payment link

  Creates an Adyen Pay by Link payment link that a shopper can open to pay the given amount.

• Action
  Cancel payment

  Cancels an authorised payment that has not been captured yet, releasing the funds back to the shopper. The final outcome arrives later in Adyen's CANCELLATION webhook.

• Action
  Capture payment

  Captures an authorised payment (full or partial amount). Adyen processes the capture asynchronously: the response always has status "received" and the final outcome arrives later in a CAPTURE webhook.

• Action
  Delete stored payment method

  Deletes (disables) a shopper's stored payment details token in Adyen.

• Action
  Get payment link

  Retrieves the details of a payment link, including its amount, status (active, completed, expired or paymentPending), url and expiry.

• Action
  List payment methods

  Retrieves the payment methods available for a transaction, based on details such as amount, country and currency, plus the shopper's stored payment methods when a shopper reference is given.

• Action
  List stored payment methods

  Lists the tokens for payment details stored for a shopper, with a summary of each stored card or account.

• Action
  Refund payment

  Refunds a captured Adyen payment, fully or partially. Adyen acknowledges the request immediately; the final outcome arrives later in a REFUND notification.

• Action
  Update payment link

  Updates the status of an Adyen payment link. Adyen only allows setting the status to expired, which forces the link to expire so shoppers can no longer pay with it.

• Trigger
  New Ticket

  Triggers when a new ticket is logged in Halo.

• Trigger
  Ticket Updated

  Triggers when a ticket is created or updated in Halo.

• Action
  Add action to ticket

  Adds a new action (note, update or outcome) to an existing Halo ticket.

• Action
  Add project

  Creates a new project in Halo and returns the created project record.

• Action
  Create Site

  Creates a new site for a customer in Halo.

• Action
  Create Ticket

  Creates a new ticket in Halo with a summary, description and optional customer, user, type, priority, status and assignment.

• Action
  Create User

  Creates a new end user in Halo under the chosen site.

• Action
  Get customer

  Returns a single Halo customer (client) by its ID, optionally with extra details and ticket activity.

• Action
  Get project

  Returns a single Halo project by its ID, including its details and custom fields.

• Action
  Get ticket

  Returns a single Halo ticket by its ID, optionally with extra details and its last action.

• Action
  Get user

  Returns a single Halo user (end-user contact) by ID, with optional details, ticket activity and pop-ups.

• Action
  List customers

  Returns a list of customers (clients) in Halo, optionally filtered by search text or top level.

• Action
  List tickets

  Returns tickets from Halo, optionally filtered by customer, agent, status, dates, search text and more.

• Action
  List users

  Returns the users (end-user contacts) in Halo, optionally filtered by customer, site, search text and other criteria.

• Action
  Update ticket

  Updates an existing Halo ticket's summary, details, customer, assignment, status, priority and category. Fields left blank are not changed.

• Action
  Update user

  Updates an existing Halo user's name, site, email or phone number. Fields left blank keep their current values.

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