Covered in this article
Related pages
Latest Changelog
Version 1.3.0 ()
Utility Component

Utility Component

A component that is designed for utility operations.

Environment variables

  • [optional] EIO_REQUIRED_RAM_MB - Number of MB allocated to container. 1024 by default
  • [optional] REQUEST_TIMEOUT - HTTP request timeout in milliseconds. 10000 by default
  • [optional] REQUEST_RETRY_DELAY - Delay between retry attempts in milliseconds. 7000 by default
  • [optional] REQUEST_MAX_RETRY - Number of HTTP request retry attempts. 7 by default
  • [optional] REQUEST_MAX_CONTENT_LENGTH - Max size of HTTP request in bytes. 10485760 by default

Technical Notes

The technical notes page gives some technical details about Utility component like changelog.


This component has no trigger functions. This means it will not be accessible to select as a first component during the integration flow design.


String To Attachment

Creates attachment from input value. Output is attachmentId and attachmentUrl in message.body and attachment object in message.attachments:

String To Attachment

Configuration fields description

  • encodeToBase64 - if checked encode an input value using Base64 encode. Than saves encoded value into attachment.

String From Attachment

Creates string from attachment with provided input attachmentId which must be either:

  • A numeric ID of the attachment that can be referenced in the step immediately prior
  • A URL to an attachment produced by any component in the flow.

String From Attachment

Configuration fields description

  • decodeFromBase64 - if checked decode attachment content using Base64 decode before output. If content of attachment is malformed or not Base64 encoded string, result will be malformed.

Base64 Decode

Decodes input value using Base64 decoding to regular string. If malformed input provided or not Base64 encoded string, result will be malformed:

Base64 Decode

Base64 Encode

Encodes input value using Base64 encoding:

Base64 Encode

Convert Between Timezones

Given two timezones and an array of timestamps (without any timezone info) converts the timestamps to the output timezone. The output is a dictionary of oldTimezone -> newTimezone values:

Convert Between Timezones

E.g. If converting from UTC to German time then

{timesToConvert: ['2020-01-01T12:00:00', '2020-07-01T12:00:00']}


  '2020-01-01T12:00:00': '2020-01-01T13:00:00+01:00',
  '2020-07-01T12:00:00': '2020-07-01T14:00:00+02:00',

This component takes into account that Germany is ahead of UTC 1 hour in Winter and 2 hours in the Summer. The possible format of incoming strings is deliberately broad to account for as large a range of possible timestamps. Epoch time conversion is not supported.


Introduce a delay before passing the message to the next step.

Config Fields

  • Delay behavior, as two options:

    • Delay Each - every incoming message will to delay independent each other, for example: we have 100 messages at the same moment with delay 1 sec, after 1 sec all messages will get to the next step.
    • Delay All - all incoming message will to delay one by one, new message will go farther only after previous finish, for example: we have 100 messages at the same moment with delay 1 sec, each second a message will go to the next step (from oldest).

Input Metadata

  • Delay Time (in seconds) - Amount of time this component should wait/delay (in seconds) before emiting the message. Negative number will be converted to positive, strings converted to number, if converted failed will set to zero.
  • Data to transfer - Use this field to transfer data in to another steps


  1. Maximal possible size for an attachment is 10 MB.
  2. Attachments mechanism does not work with Local Agent Installation.
  3. Delay All option from Delay don’t correctly support Parallel Processing option in component more then 1
  4. Delay Each option from Delay in ordinary flow type can handle delay up to 30 sec, if you need more, use real-time type
  5. Needs to use Data to transfer field for correct transfer data after Delay component.

Click here to learn more about the iPaaS