Creating a Rule

You need to configure the publisher, its events, and target types beforehand to use them within the rule. Webhooks can be configured within the Signals service; functions and circuits can be created in the Catalyst Serverless platform.

I. Configuring the Event Source

  1. Navigate to the Rules section and click the Add Rule button.
Rules Home Page
  1. Provide a Name and Description for the rule in the title bar, as shown in this image.
Providing rule name and description
  1. Click on Choose Events.

This will open a pop-up displaying the configured publishers from Zoho Publishers, SAAS Partner Publishers, and Custom Publishers.

Select a publisher and choose an event from it.

Choosing a publisher and an event

II. Setting up the Filter

  1. Select the edit icon of the filter to determine which events you want to be sent to the target.
Applying filter to the rule

You can choose to deliver all events or create conditions to filter and only share the required events with the target.

  1. Select the Events matching certain conditions option and provide the condition.
Creating criteria for the filter

The Path key in the filter lists all the properties of that particular event in payload. The following comparators are supported for creating a filter in the rule:

Data Type Supported Comparators
String is, isn't, contains, doesn\'t contain, starts with, ends with, is empty, is not empty
Integer, Number = (equals), != (not equals), < (less than), <= (lesser than or equals), > (greater than), >= (greater than or equals), between, not between, is empty, is not empty
Boolean is, isn't
DateTime, Date is, isn't, is before, is after, between, not between, is empty, is not empty, Today, Tomorrow, Tomorrow Onwards, Yesterday, Till Yesterday, Last Month, Current Month, Next Month, Last Week, Current Week, Next Week

III. Configuring Dispatch Actions

  1. Click the Choose Target button.
Creating a target for rule
  1. In the pop-up window, provide the Target Name and choose your Consumer Type.
Configuring the target
  1. Upon selecting the preferred consumer type, you need to choose the respective webhook / function / circuit for the rule.
Choosing the target type

Placeholders

If you have chosen a webhook with dynamic values in headers or parameters, a new field called Placeholders will appear, as shown in the image.

Customized headers and parameters
  • Specify the values for the keys configured in the webhooks page for headers/parameters.
Providing static value to the placeholder
  • You can either provide static values or dynamic values using JSON path of the event schema. Use JSON path to denote the key whose values you want to use.
Providing a variable value to the placeholder
  1. Provide the number of retry attempts that should take place when any event fails to reach the target.

Learn more about invocation policies

Invocation Policy in Catalyst Signals
  1. Provide the number of retry attempts that should take place when any event fails to reach the target.
Providing number of retry attempts

You can also set the frequency of retries based on your needs. Check this help page to know more about the frequency of retry attempts.

  1. In the Target Input, you can either deliver the complete event schema to the target or perform extraction and transformation based on your business requirements before delivering it to the target.

Extraction

  • Select the Extraction option under Target Input.

  • The Path field will list you all the keys in terms of JSON path from the particular event schema. You can only select and extract a single key from the event schema.

Extracting the desired key from an event.

Transformation

Learn how to transform your schema

  • Select the Transformation option under Target Input.

A three-pane transformer will appear with a sample event payload on your left.

Transforming the desired keys of an event
  • In the center pane, build a JSON body with the custom keys that you would require for your target.
Building a custom JSON body
  • In place of providing values to the keys, you can match the values from the default event payload.

Refer to the sample event payload on the left and provide the JSON path of the key whose value you would want for the keys in the compiler.

Mapping keys from the event payload
  • Click the Generate Output button in the right pane. This will provide the transformed payload with the custom keys mapped to the data from the default payload.
Generating customized event body

Signlas will use the generated output as the new payload for the particular target in this rule. Once you have completed your transformation, click the Confirm button.

Learn more about event transformation and its guidelines

  1. Similarly, you can add a maximum of five targets to a rule. After adding the targets, click the Save button in the top-right corner.
Saving the rule

Last Updated 2025-04-11 18:35:15 +0530 +0530