Skip to main content

Create event actions

Goal​

To set up automated actions that trigger when specific events occur in the Propeller backoffice. Event actions enable automated emails, webhook notifications and other responses to system events like order creation, customer registration or quote requests.

For more technical documentation including payload examples and implementation details, see Event and Template Configuration.

Step 1: Navigate to Event Actions​

  1. From the backoffice menu, select Shops & Channels and then Event Actions.
  2. You'll see a list of existing event actions showing:
    • Name
    • Trigger event
    • Code (for custom events)
    • Action type
    • URL (for webhooks)
    • Date Created
    • Date Updated

Step 2: Create a New Event Action​

  1. Click the New Event Action button in the top right corner.
  2. A popup window titled New Event Action will appear.

Step 3: Select Action Type​

Choose the type of action to perform:

Send Email​

  • Sends an automated email using a template
  • Requires selecting an email template
  • Email is sent to recipients defined in the template

Post to Webhook​

  • Sends event data to an external URL
  • Useful for integrations with external systems
  • Sends the full event payload as JSON

Toggle between the two options using the tabs at the top of the form.

Step 4: Configure Event Trigger​

  1. Event Trigger: Select from the dropdown which event should trigger this action:

    • ORDER_CREATED: Triggered when a new order or quote is created
    • ORDER_UPDATED: Triggered when an existing order or quote is updated
    • ORDER_DELETED: Triggered when an existing order or quote is deleted
    • ORDER_SEND_CONFIRMATION: Triggered for sending order confirmation emails (checkout process or 'Send order to client' button in Sales Portal)
    • QUOTE_SEND: Triggered to send quote proposals to contacts (via 'Send to client' button in Sales Portal)
    • QUOTE_SEND_REQUEST: Triggered to send confirmation after a quote is requested by a customer
    • QUOTE_SEND_VALIDATION: Triggered to send quotes to senior managers for validation
    • CART_PURCHASE_AUTHORIZATION_REQUEST_SEND: Triggered to send purchase authorization requests to authorization managers
    • CONTACT_SEND_WELCOME_EMAIL: Triggered to send welcome emails to new contacts
    • CUSTOMER_SEND_WELCOME_EMAIL: Triggered to send welcome emails to new customers
    • SEND_RESET_PASSWORD: Triggered to send password reset emails
    • SEND_INIT_PASSWORD: Triggered to send initial password setup emails
    • CUSTOM_EVENT: Used to trigger events with custom payloads

  2. Name (NL): Enter a descriptive name for this event action

    • Use the language dropdown to set names in different languages
    • This name appears in the event actions list

  3. Code: Optionally, enter a unique code identifier

Step 5: Configure Action-Specific Settings​

For Email Actions​

  1. Select email template: Choose from available templates
    • Templates are managed separately in the Templates section
    • The template ID will be displayed once selected

For Webhook Actions​

  1. Url: Enter the complete webhook endpoint URL
    • Must be a valid HTTPS URL
    • Example: https://webhook.site/509ff9f4-9e24-46c8-ba4c-8bc27bd779af
    • The URL will receive POST requests with event data

Step 6: Save the Event Action​

  1. Click Save to create the event action.
  2. The popup will close and the new action will appear in the list.
  3. Click Cancel to discard changes.

Editing Event Actions​

  1. Click on any event action in the list to edit it.
  2. The Edit Event Action popup shows current settings.
  3. You can change:
    • Action type (Email/Webhook)
    • Event trigger
    • Name
    • Template or URL
  4. Click Save to apply changes.

Webhook Security (Coming Soon)​

Advanced webhook security features are available through the API but not yet in the UI:

HMAC Signature Verification​

  • Signature Salt: A secret key used to generate HMAC-SHA256 signatures
  • When configured, webhooks include an X-Propeller-Signature header
  • Format: sha256=<signature>
  • Allows webhook endpoints to verify the payload authenticity

Basic Authentication​

  • Username & Password: HTTP Basic Authentication credentials
  • Both fields must be provided together
  • Password is stored securely and never displayed after saving
  • Adds Authorization: Basic <credentials> header to webhook requests

Note: These security features can currently only be configured via API. UI support is planned for a future release.