Processes: Standard Tasks: Data Container

The 'data container' plugin allows you to create a custom endpoint that can receive posted JSON data and stores it as instance data in your Integrify database. This task is designed to be completed by an API POST. Once the workflow reaches the data container task, the endpoint is prepped to wait for data to be posted to it. Once the data is posted, the workflow moves forward.

How it Works

  • You add a data container task type to your workflow.
  • You configure the task, defining an expected field configuration with specific keys and data types.
  • Field Configuration: This shows which fields from your post body to store in the database (the other fields are ignored). None of the fields will be required in the post body, so you can include as many as you would like in the post body without producing an error.
  • Data Types: The expected data types for each field, such as 'string', 'numeric', or 'date'.

Checking for Endpoints Programmatically

You can always find your endpoint in the request summary, but you can also programmatically check for endpoints by sending a GET request to:


You can optionally filter by task name, instance ID, or instance SID. See complete filtering options at

Here is an example response that shows two ready endpoints:

  endpoints: [

As a convenience, the task name is appended to each endpoint in the response for easier visual parsing and searching. When a GET or POST request is made to the endpoint, this 'task_name' querystring will be ignored if included.

Here is an example response that includes no endpoints:

    endpoints: [ ]

Getting the Field Configuration

Each endpoint will accept a GET request or a POST request.

  • GET
    • Returns the field configuration for your endpoint, in case you need to know what field keys and data types are expected.

Here is an example field configuration

    field_configuration: [
            key: "client_name",
            value_type: "string"
            key: "client_number",
            value_type: "numeric"

See more information at

Posting Data

  • POST
    • Stores any data fields from the post body that match the expected field configuration.
    • Completes the task and pushes the workflow to the next task.

Here is an example post body:

    "client_name": "John Doe",
    "client_number": 5


See more information at


Powered by Zendesk