Copy page

Tines

Event Stream

Collects workflow and alert events from your Tines tenant for automation visibility and monitoring.

Sync Type: Incremental

Requirements

Before you connect Monad to Tines, you need an API Key and a Tenant URL:

1. Sign up for a Tines tenant to get a Tenant URL if you aren't already a customer.
2. Follow the instructions in the following link from Tines to generate an API Key to allow API access to event data - https://www.tines.com/api/authentication/

Details

Monad uses the since filter on the API to determine which events to display. This field is updated every time a request to get events is successful with the last time a request to get events was initiated. If this was the first time requesting for data, a full sync of the data is performed.

Configuration

The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.

Settings

Setting	Type	Required	Description
Tenant URL	string	Yes	Unique URL for your Tines instance.
Team ID	string	No	Filter by the given team.
Story ID	string	No	Filter by the given story.
Backfill Start Time	string	No	The date to start fetching data from. If not specified, no past records will be fetched.
API Rate Limit	object	No	Optional limit on the connector's outbound request rate to the source API. Leave blank to use the connector's default behavior. See API Rate Limiting for the field format, limits, and how to choose a value.

Secrets

Secret	Type	Required	Description
API Key	string	Yes	API Key for the Tines API. This is required to authenticate requests.

Related Articles

https://www.tines.com/api/events/list/ https://www.tines.com/api/authentication/

Sample Record

Code
{
  "id": 1508459857,
  "user_id": 22,
  "agent_id": 156,
  "payload": {
    "propagation_webhook": {
      "username": "Peter Brown",
      "age": 88
    },
    "delay_http_request": {
      "body": {
        "delay": "7"
      },
      "headers": {
        "access-control-allow-credentials": "",
        "access-control-allow-headers": "",
        "access-control-allow-methods": "",
        "access-control-allow-origin": "",
        "access-control-expose-headers": "",
        "content-type": "application/x-www-form-urlencoded",
        "date": "2025-08-11T23:46:24Z",
        "etag": "W/\"931-08571773-6abd-3632-afd3-16e3b36915ca\"",
        "server": "apache",
        "set-cookie": "sails.sid=s%3A11563e82-bc81-9a21-b60a-79773c70f959; Path=/; HttpOnly",
        "vary": "Accept-Encoding",
        "content-length": "994",
        "connection": "Close"
      },
      "status": 204
    }
  },
  "created_at": "2025-08-11T23:46:24.244678Z",
  "updated_at": "2025-08-11T23:46:24.244683Z",
  "story_run_guid": "33366377-34d0-62a3-3ca8-e74c94060237",
  "previous_events_ids": [
    1054452026
  ]
}

Sync frequency

By default this input polls approximately every 10 seconds, with each sync beginning after the previous one completes. A cron schedule configured on the pipeline overrides this cadence. See Input Sync Frequency for details.