Skip to main content

Create an event action

Goal​

To automate email notifications or webhook calls based on specific system events such as order creation, quote submission or password resets. This ensures consistent communication and integration with external systems using the Event Action module in the Propeller backoffice.

Step 1: Navigate to the Event Actions Section​

  1. From the backoffice menu, go to Admin and click Event Actions.
  2. The Event Actions page lists all existing event-driven actions with details like Name, Trigger, Action Type and Dates.

Step 2: Click ‘New Event Action’​

  1. In the Event Actions list view, click the New Event Action button in the top right corner.
  2. A new form will appear as a pop up, allowing you to configure the event action.

Step 3: Select the Action Type​

  1. Choose one of the following options:
    • Send Email – To trigger an email based on a template.
    • Post to Webhook – To send the event payload to a third-party endpoint.

Use the toggle to switch between the two modes.

Step 4: Fill in Event Action Details​

  1. Event Trigger: Select the system event that should trigger this action. Examples include:
    • ORDER_CREATED – When an order or quote is created
    • QUOTE_SEND – When a quote is sent from the sales portal to the contact
    • SEND_RESET_PASSWORD – When a user resets their password
  2. Name: Enter a name for this action (e.g., “Order created notification”).
  3. Code: Enter a short code that uniquely identifies this action (e.g., order-created-notification) for technical reference.
  4. Fill the URL or email template relevant for this event action.
    • URL (only for Webhook event actions): Enter the destination URL if the action should post data to a webhook.
    • Select email template (only for Email event actions): Choose the template which will be used to generate and send emails.

Step 5: Save the Event Action​

  • After completing all fields, click Save at the bottom of the pop up.
  • Your new event action will now appear in the Event Actions list and will be triggered when the selected event occurs.

Best Practices​

  • Use clear names and codes: Make it easy to understand what each action does without reading the full configuration.
  • Email Templates must exist: Make sure you’ve already created and tested the associated email template if using the Send Email action.
  • Test before enabling: Use a test trigger or staging environment to verify the event action behaves as expected.
  • Re-use events: You can configure multiple actions (email + webhook) for the same event trigger if needed, by creating multiple event actions.