Connect Vyte to GoCardless

Both apps 34Vyte 16GoCardless 18

• Trigger
  Event Cancelled

  Triggers when an event is cancelled.

• Trigger
  Event Confirmed

  Triggers when an event is confirmed.

• Trigger
  Event Created

  Fires when a Vyte event is created (including events created already confirmed).

• Action
  Add appointment type

  Create a new appointment type on a Vyteme booking page.

• Action
  Add invitee

  Add one or more invitees to an existing event.

• Action
  Add user

  Creates a user in your Vyte organization.

• Action
  Cancel Event

  Cancels a Vyte event. Vyte has no delete for events; cancelling is how an event is removed from scheduling.

• Action
  Confirm Event

  Confirms a Vyte event on a chosen date and place.

• Action
  Create Event

  Creates an event

• Action
  Delete user

  Removes a user from your Vyte organization so you are no longer billed for them. This does not delete the person's Vyte account.

• Action
  Find available slots by user

  Returns the free time slots at which the specified Vyte users (by email or user id) or team are all available, for a given appointment duration and date range.

• Action
  Get Event

  Retrieve a single Vyte event by its id.

• Action
  List Users

  Lists all users linked to your Vyte organization.

• Action
  Update appointment type

  Update an existing appointment type's settings.

• Action
  Update Event

  Updates an existing Vyte event's title, proposed dates or proposed places.

• Action
  Update user

  Update a user's profile (name, timezone, language, etc).

• Action
  Add billing request

  Creates a GoCardless billing request to collect a Direct Debit mandate, a one-off payment, or both from a customer.

• Action
  Add customer

  Creates a new customer record in GoCardless with their name, contact details and address.

• Action
  Add customer bank account

  Creates a bank account for an existing GoCardless customer, using local bank details or an IBAN.

• Action
  Cancel mandate

  Cancels a Direct Debit mandate so no further payments can be collected against it, and returns the cancelled mandate.

• Action
  Cancel payment

  Cancels a pending GoCardless payment so it is not collected, and returns the updated payment.

• Action
  Cancel subscription

  Cancels a GoCardless subscription so no further payments are collected under it, and returns the cancelled subscription.

• Action
  Create Direct Debit Payment

  Collects a one-off Direct Debit payment from a customer against their existing mandate.

• Action
  Create Instant Bank Payment

  Creates a billing request for a one-off instant bank payment (Pay By Bank) for the given amount and currency.

• Action
  Create Mandate Authorisation Request

  Creates a Direct Debit mandate request for a payer and returns a hosted authorisation link you can send them to set up the mandate.

• Action
  Create Subscription

  Creates a recurring subscription that collects a fixed amount on a schedule against an existing GoCardless mandate.

• Action
  Get customer

  Returns a single GoCardless customer by its ID, including contact details, address and metadata.

• Action
  Get mandate

  Returns a single Direct Debit mandate, including its status, scheme, reference and linked customer bank account and creditor.

• Action
  Get payment

  Returns a single GoCardless payment by its ID, including amount, status, charge date and linked mandate.

• Action
  Get subscription

  Returns the details of a single GoCardless subscription, including its amount, schedule, status and upcoming payments.

• Action
  Retry payment

  Retries a failed payment, resubmitting it for collection on the next available date or a date you choose.

• Action
  Search for a Billing Request

  Searches billing requests, optionally filtered by customer, status and creation date, and returns the matches.

• Action
  Search for a Customer

  Searches your GoCardless customers by email, company name, surname, currency or creation date and returns the matches.

• Action
  Update customer

  Updates an existing GoCardless customer's name, contact details, address or metadata. Fields left blank are not changed.

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