Custom Rule Actions

Last updated last month

This tutorial teaches you how to write a custom rule action.

You have to create several components in C# and angular:

  1. [C#] The definition of the rule action.

  2. [C#] The action handler to execute the rule action.

  3. [Angular] The editor to edit the rule action.

Our example

In this example we will write an action that adds a new line to a predefined file whenever an event happened.

We call this action AppendToFile.

Typically you want to create an action to communicate with external services, but this example shows all essential parts.

Step1: Backend code

We create two files in the extension project:

  1. AppendToFileAction.cs: The action definition and data model. This file and class must be named <ACTION-TYPE>Action.

  2. AppendToFileActionHandler.cs: The action handler to execute the rule action.

New C# files

Step 1.1: The Action definition

Lets have a look to the file first:

// AppendToFileAction.cs
using System.ComponentModel.DataAnnotations;
using Squidex.Domain.Apps.Core.Rules;
namespace Squidex.Extensions.Actions.WriteToFile
[RuleActionHandler(typeof(AppendToFileActionHandler))] // 1
[RuleAction( // 2
IconImage = "<svg xmlns='' viewBox='0 0 28 28'></svg>",
IconColor = "#4bb958",
Display = "Append to file",
Description = "Append text to a file",
ReadMore = "")]
public sealed class AppendToFileAction : RuleAction
[Required] // 3
[Display(Name = "Text", Description = "The text to append to the file.")] // 4
public string Text { get; set; } // 5, 6

This class has several purposes:

  1. It defines the action handler that is used to execute this action.

  2. It contains a lot of metadata about the rule action such as:

    • The color of the icon.

    • The svg for the icon.

    • A short description that is used in rule overview (Display).

    • A long description that is used when you create a new rule (Description).

    • A url to the product or additional information such as documentation.

  3. It contains attributes for validation, in this case the text attribute is required.

  4. It contains metadata for the properties that are used when the API documentation is generated.

  5. It is used to deserialize the json from the API requests.

  6. It is used to serialize and deserialize the rule in the database.

Therefore it is important that the rule action is serializable. We use the widely adopted Newtonsoft.Json library for that:

About the Icon:

You have to define the icon as svg content. Here are some tipps:

Step 1.2. The Action handler

The action handler is executed two times:

  1. When an event happened, e.g. when a content has been published, the action handler is executed to create a job. The job must contain all information to execute the action at a later point of time. When the action is executed (typically a few ms later for the first time) it has no access to the event anymore. The advantage is that the action can be executed multiple times, e.g. to retry it when an external service is temporarily not available.

  2. The scheduler takes the job and calls the action handler again to execute the job.

The following code is a simple implementation for our action:

// AppendToFileActionHandler.cs
using System;
using System.IO;
using System.Threading.Tasks;
using Squidex.Domain.Apps.Core.HandleRules;
using Squidex.Domain.Apps.Core.HandleRules.EnrichedEvents;
namespace Squidex.Extensions.Actions.WriteToFile
public sealed class AppendToFileActionHandler
: RuleActionHandler<AppendToFileAction, AppendToFileJob>
public AppendToFileActionHandler(RuleEventFormatter formatter)
: base(formatter)
protected override (string Description, AppendToFileJob Data) CreateJob(
EnrichedEvent @event, AppendToFileAction action)
// Use event to format the text and allow some placeholder
// such as content data, user information, timestamps and so on.
var text = Format(action.Text, @event);
// Create a description for the logs and the job.
return ("Append to file.", new AppendToFileJob { Text = text });
protected override Task<(string Dump, Exception Exception)> ExecuteJobAsync(
AppendToFileJob job)
// Do the action.
File.AppendAllText("PATH-TO-FILE", job.Text);
// Creates a dump with all ikmportant information for debugging.
return Task.FromResult(("Appended to file PATH-TO-FILE", (Exception)null));
public sealed class AppendToFileJob
public string Text { get; set; }

Step 2: Frontend code

The frontend code must be written in angular, but you do not have to learn it, you can just copy and paste all essential parts from other actions. You do not have to read the full documentation but it might be helpful to read the guide about forms:

We have to create an angular component to define the form for our action.

New Angular files

We create three files: The component (typescript), the styles (sass) and the template (html).

Step 2.1. Create the component

The typescript file contains our component and extends the form with the controls. We have to create one form control for each property in our form action. We also add client-side validation here.

// append-to-file-action.component.ts
import { Component, Input, OnInit } from '@angular/core';
import { FormControl, FormGroup, Validators } from '@angular/forms';
selector: 'sqx-append-to-file-action',
styleUrls: ['./append-to-file-action.component.scss'],
templateUrl: './append-to-file-action.component.html'
export class AppendToFileActionComponent implements OnInit {
public action: any;
public actionForm: FormGroup;
public actionFormSubmitted = false;
public ngOnInit() {
new FormControl(this.action.text || '', [

Step 2.2: Create the component template

The template is just a bootstrap template that is binded to the form control.

<form [formGroup]="actionForm" class="form-horizontal">
<div class="form-group row">
<label class="col col-3 col-form-label" for="text">Text</label>
<div class="col col-9">
<sqx-control-errors for="text" [submitted]="actionFormSubmitted"></sqx-control-errors>
<textarea class="form-control" id="text" formControlName="text"></textarea>
<small class="form-text text-muted">
The text to append to the file. Read the <a routerLink="help">help</a> section for information about advanced formatting.

Step 2.3: Define the component styles

We just increase the height of textarea here. Angular isolates the css for each component, so this css rule is only applied to the textarea of the component.

@import '_vars';
@import '_mixins';
textarea {
height: 150px;

Step 2.4: Register the component

Unfortunanetly we have to register the component in several places. It is a restriction from angular and we are looking for a better solution.

New Changed files

Step 2.4.1: rule-wizard.component.html: Extend the switch statement to render the correct form based on the action type

<sqx-modal-dialog ...>
<ng-container title>
<ng-container content>
<ng-container *ngIf="step === 4">
<form [formGroup]="actionForm.form" (submit)="saveAction()">
<h3 class="wizard-title">{{ruleActions[actionType].display}}</h3>
<ng-container [ngSwitch]="actionType">
<!-- Add our component -->
<ng-container *ngSwitchCase="'AppendToFile'">
[actionFormSubmitted]="actionForm.submitted | async">
<ng-container footer>

Step 2.4.2: declarations.ts: Export the new component

// declarations.ts
export * from './pages/rules/actions/algolia-action.component';
export * from './pages/rules/actions/append-to-file-action.component'; // Add our component
export * from './pages/rules/actions/webhook-action.component';

Step 2.4.3: module.ts: Import and register the new component

// module.ts
import {
AppendToFileActionComponent, // Import the new component
} from './declarations';
imports: [
declarations: [
AppendToFileActionComponent, // Register the new component.
export class SqxFeatureRulesModule { }

Thats it, you are done. I hope to see a pull request for a new action soon.