Connect Adyen to Flodesk

Both apps 27Adyen 12Flodesk 15

• 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.

• Action
  Add custom field

  Creates a new subscriber custom field in your Flodesk account with the label you choose.

• Action
  Add Existing Subscriber to Segment

  Adds an existing Flodesk subscriber to one or more segments and returns the updated subscriber.

• Action
  Add Existing Subscriber to Workflow

  Adds an existing Flodesk subscriber to a workflow, identified by subscriber ID or email address.

• Action
  Add segment

  Creates a new segment in your Flodesk account and returns it.

• Action
  Create/Update Subscriber

  Creates a new Flodesk subscriber, or updates the existing one with the same email address or id, optionally adding them to segments.

• Action
  Find a Subscriber by Email Address

  Looks up a Flodesk subscriber by email address and returns their status, name, segments and custom field values.

• Action
  Get segment

  Returns a single Flodesk segment, including its name, color, type and number of active subscribers.

• Action
  List campaigns

  Returns the email campaigns in your Flodesk account, optionally filtered by status or a search term.

• Action
  List custom fields

  Returns every subscriber custom field defined in your Flodesk account, with each field's key and display label.

• Action
  List segments

  Returns all segments in your Flodesk account, with each segment's name, color, type and active subscriber count.

• Action
  List subscribers

  Returns subscribers in your Flodesk account, optionally filtered by status or segment.

• Action
  List workflows

  Returns the workflows in your Flodesk account, optionally filtered by status (active, paused or draft).

• Action
  Remove Existing Subscriber From Segment

  Removes an existing Flodesk subscriber from one or more segments and returns the updated subscriber.

• Action
  Remove Existing Subscriber From Workflow

  Removes an existing subscriber, identified by subscriber ID or email address, from a Flodesk workflow.

• Action
  Unsubscribe Subscriber

  Unsubscribes a subscriber from all of your Flodesk lists so they no longer receive marketing emails, and returns the updated subscriber.

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