Please note that we have changed the menu structure.To simplify navigation, your elopage account is now structured slightly differently. But the functions remain the same. We will adjust the help section and renew the screenshots. If you have any questions, our support will be happy to help.
Achtung, neue Menüstruktur! Um die Navigation zu vereinfachen, ist dein elopage-Account jetzt etwas anders strukturiert. Die Funktionen bleiben aber die gleichen. Wir werden den Hilfebereich anpassen und die Screenshots erneuern. Bei Fragen hilft unser Support gerne weiter.
This is a machine-translated article. We’re constantly working on improving translation quality for an optimized help center experience. We apologize for any inconvenience.

Zapier trigger "Order State Updates"

Neda Najjari
Neda Najjari
  • Updated

With the trigger "Order State Updates" you receive information about

  • when a new order has been placed and
  • the status of the order changes

In the dashboard you can find all orders and the current status of the order under "Customers: and "Orders."

When is the trigger triggered?

The trigger is triggered at

  • Creation of an order, regardless of how the pricing plan is set and whether a payment has been received or not. 
  • The change in the order status (incoming payment, incorrect payment, missing payment on the due date, repayment of a partial amount through your support, receipt of a chargeback, termination of a subscription by the customer, blocking access to the course under "Access").

Examples of the use of the trigger

You can then use this information for further manual or automated actions such as

  • setting up external access to your product after receipt of payment and sending the email with the access data after payment has been received or an order with purchase on account or a test period has been received
  • blocking external access to your product as soon as the customers end their subscription
  • manually deleting the customer from your Facebook group belonging to the product if the payment is missing or the subscription is ended
  • sending a payment reminder
  • triggering an email to a specific email (e.g. your contract management)

Setting up triggers


Then provide actions that are to occur when the trigger has been tripped. To do this, you usually connect another app to forward the selected data to another application.

Payment status

The decisive factor in this zap is the payment status. Here you can see whether a payment has been made, whether it has not been paid or whether it has been canceled.

  • payment_pending = Payment waiting for finalization
  • active_subscription = Payment active, installments due up to now have been paid
  • paid = all installments were paid 
  • payment_paused = Pricing plan paused because a due payment has not been received 
  • subscription_cancelled = Subscription ended, no further payments are due
  • payment_refunded = at least one payment was canceled / repaid
  • payment_not_completed = payment waiting for finalization that is not confirmed and therefore changes to the "expired" status after a few days

Which data are transmitted?

Order data

  • Action (subscription_state_changed) - here you can find out what exactly has changed
  • Payment Session Token - Token
  • Payment State - payment status
  • Created - date of creation
  • Opt ins
  • Opt Ins Answer (answer to question from a custom field)
  • Opt into Question (question from a custom field)
  • Opt ins Question ID (ID of the question from a custom field)

Buyer data

  • Payer First Name - First name
  • Payer Last Name - Last name
  • Payer Company - Company-
  • Payer Phone - phone number
  • Payer VAT No - tax number
  • Payer City - city
  • Payer Country - country
  • Payer Email - Email address
  • Payer Street - street
  • Payer Street Number - house number
  • Payer Zip - Postal Code

Pricing plan data 

  • Product Price - product price
  • Pricing Plan Name - Name of the pricing plan
  • Currency - currency
  • With Custom Start - fixed due date
  • With Test Period - test period
  • Payments Count - the number of installments paid
  • Payments Count Expected - expected number of installments (for a limited subscription and installment payment)
  • Payments Schedule - Payment data for multiple payments
  • Payments Schedule Amount - the amount of the installment
  • Payment Schedule Date - the due date
  • Payment schedule rate
  • Payments Schedule State - status of the installments
  • Payment Method - payment method
  • Recurring - recurring
  • Recurring Form - type of pricing plan (subscription, limited subscription, installment payment)

Product data

  • Product name - product name
  • Product ID - Product ID
  • Product Slug - URL
  • Product Type - product type
  • Events (events for the eTicket)
  • Tickets (tickets for the eTicket)
  • Tickets codes - ticket number
  • Tickets Count - number of tickets
  • Ticket Reserved Invoices Count - number of reserved tickets

Was this article helpful?