JovianX Platform for SaaS
  • ⛅Introduction to JovianX
  • 🔰Getting Started with JovianX
  • ✨Release Notes
  • Product Documentation
    • Dashboard
    • Accounts
    • Blueprints
    • Plans
    • Settings
      • Infrastructure
      • Customer Console
        • Emails Blacklist
      • Email Notifications
      • Automation
      • Payments
      • Members
  • Guides
    • Integrations
      • PagerDuty + JovianX Integration
    • Adding Clusters to JovianX
    • New Cluster Considerations
    • Creating AWS ELK Cluster
    • Creating Azure AKS Cluster
    • Kubernetes Cluster System Components
Powered by GitBook
On this page
  • Events‌
  • Actions
  • Available Variables
  • Creating a new automation Rule

Was this helpful?

  1. Product Documentation
  2. Settings

Automation

PreviousEmail NotificationsNextPayments

Last updated 5 years ago

Was this helpful?

Automation allows creating automation rules, that trigger actions based on JovianX events. Once a rule is triggered it calls an action webhook, that can send information from JovianX to external cloud services. Automation effectively allows integration with external services such as , , , , and others.

Events‌

JovianX allows configuring automation rules for the following events:

  • Customer account created

  • Customer account deleted

  • Customer account trial is over

  • Customer account user created

  • Customer account user logged in

  • Application helm parameters changed

  • Application launch settings changed

  • Application upgraded

  • Application error

  • Email notification sent

Actions

JovianX supports the following action Types:

Webhook

JovianX calls a webhook when an automation rule is triggered. ‌To configure a Webhook set the following settings:

URL

The URL of the Webhook Must be a valid web address URI.

‌Method

You can define the URL method for JovianX to trigger, following methods are supported:

  • GET

  • POST

  • PUT

  • PATCH

Headers

Custom headers are supported, you can define a custom key: value pairs of headers. Additionally, you can use variables as header values:

Content:

The content section holds the Webhook request content data, you can define the content type and configure the data to send.

Content Type

  • JSON

  • MULTIPART/FORM-DATA

  • X-WWW-FORM-URLENCODED

JSON content-type allows defining the JSON content data:

MULTIPART/FORM-DATA and X-WWW-FORM-URLENCODED allow setting the key:value data:

Available Variables

Events expose a set of variables that can be used as event data or headers when triggering an action:

Event

Supported Variables

Customer account created

Event triggered on successful customer account creation.

{{account_id}}: Account identifier

{{account_display_name}}: Account company name provided during registration

Customer account deleted

Event triggered on deletion of customer account.

{{account_id}}: Account identifier

{{account_display_name}}: Account company name provided during registration

Customer account trial is over

Event triggered when customer account trial period is over.

{{account_id}}: Account identifier

{{account_display_name}}: Account company name provided during registration

Customer account user created

Event triggered on creation of new account user

{{account_id}}: Account identifier

{{account_display_name}}: Account company name provided during registration

{{user_email}}: User email address

{{user_name}}: User full name

Customer account user logged in

Event triggered when account user logs into the customer console.

{{account_id}}: Account identifier

{{account_display_name}}: Account company name provided during registration

{{user_email}}: User email address

{{user_name}}: User full name

Application helm parameters changed

Event triggered on update of application ' 'components helm parameters.

{{account_id}}: Account identifier

{{account_display_name}}: Account company name provided during registration

{{parameters}}: Application components helm parameters after successful update

Application launch settings changed

Event triggered when account settings are changed.

{{account_id}}: Account identifier

{{account_display_name}}: Account company name provided during registration

{{parameters}}: Application components helm parameters after successful update

{{application_settings}}: New application settings chosen by user.

Application upgraded

Event triggered after successful application blueprint ' 'version change.

{{account_id}}: Account identifier

{{account_display_name}}: Account company name provided during registration

{{parameters}}: Application components helm parameters after successful upgrade.

{{old_blueprint_version}}: Application blueprint version before upgrade

{{new_blueprint_version}}: Application blueprint version after upgrade

Application error

Event triggered when application state changes to "error".

{{account_id}}: Account identifier

{{account_display_name}}: Account company name provided during registration

{{previous_state}}: Application state before it was changed to "error"

{{parameters}}: Application components helm parameters

{{application_settings}}: Application settings chosen by user

Email notification sent

Event triggered after an email notification is sent.

{{account_id}}: Account identifier

{{account_display_name}}: Account company name provided during registration

{{receiver}}: To whom notification was sent

{{subject}}: Subject of the email notification

{{message}}: Body of the email notification

Creating a new automation Rule

To create a new automation rule :

  1. Navigate to Settings > Automation on the side-menu.

  2. Click on Create rule button on the upper left side

Example JovianX > Slack integration:

HubSpot
Slack
Jira
Freshdesk
Pager Duty