Utilities

Bucket for miscellaneous utility integrations

Integration with LogicHub

Connecting with Utilities

To connect to Utilities following details are required

Actions with Utilities

Render Template

Render a given Jinja2 template with the column values of the parent table. Note that the template text is output-agnostic, so it can be Markdown, HTML, or whatever format you like.

Inputs to this Action:

  • Connection: Choose a connection that you have created.
  • Template Text: The Jinja2 template text. e.g. - Here is some sample text with {{columnName}}
  • Auto-escape HTML: Specify whether the substituted text should be automatically HTML-escaped. It is a select type field with two options - Yes and No.

Output of Action:
JSON containing the following items:

  • has_error: True/False
  • error: message/null
  • result: A JSON with rendered jinja2 template as shown in Fig 3. The input to integration is in Fig 2.
Fig 1Fig 1

Fig 1

Fig 2Fig 2

Fig 2

Fig 3Fig 3

Fig 3

Render Template Across Entire Table

Render a given Jinja2 template with the column values of the parent table. Note that the template text is output-agnostic, so it can be Markdown, HTML, or whatever format you like.

Inputs to this Action:

  • Connection: Choose a connection that you have created.
  • Template Text: The Jinja2 template text. Here is some sample text with {{rows}}
  • Auto-escape HTML: Specify whether the substituted text should be automatically HTML-escaped. It is a select type field with two options - Yes and No.

Output of Action:
JSON containing the following items:

  • has_error: True/False
  • error: message/null
  • result: A json with rendered jinja2 template as shown in Fig 6. The input to integration is in Fig 2.
Fig 4Fig 4

Fig 4

Fig 5
The output is HTML-escapedFig 5
The output is HTML-escaped

Fig 5
The output is HTML-escaped

Fig 6
The output is not HTML-escapedFig 6
The output is not HTML-escaped

Fig 6
The output is not HTML-escaped

Extract with Regexes

Searches for regexes in the input data, returns matching groups.

Inputs to this Action:

  • Connection: Choose a connection that you have created.
  • The regexes to search: A YAML dictionary with the regexes to use - keys are the column names, values are the regexes to use. Regexes need to have one group.
  • The column with the data to analyze: Column from the parent table containing data to analyze.
    Output of Action:
    JSON containing the following items:
  • has_error: True/False
  • error: message/null
  • result: A JSON containing values matched with regex as shown in Fig 8. The input to integration is in Fig 2.
Fig 7Fig 7

Fig 7

Fig 8Fig 8

Fig 8


Did this page help you?