POST
/
api
/
v1
/
streams
/
data-management
/
workflows
Workflow
curl --request POST \
  --url https://api.allium.so/api/v1/streams/data-management/workflows \
  --header 'Content-Type: application/json' \
  --header 'X-API-KEY: <api-key>' \
  --data '{
  "description": "<string>",
  "filter_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "data_source_config": {
    "type": "PUBSUB",
    "topic": "<string>"
  },
  "data_destination_config": {
    "type": "PUBSUB",
    "delivery_type": "PULL",
    "webhook_url": "<string>"
  }
}'
{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "description": "<string>",
  "filter_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "data_source_config": {
    "type": "PUBSUB",
    "topic": "<string>"
  },
  "data_destination_config": {
    "type": "PUBSUB",
    "delivery_type": "PULL",
    "webhook_url": "<string>"
  },
  "external_workflow_id": "<string>"
}
Check out this page for more details on creating a filter! Important notes
  1. In PubSub, a full topic resource name is in the format of projects/{project_id}/topics/{topic_name}. However, for specifying the topic value for data_source_config, you ONLY need to specify the {topic_name}, for e.g ethereum.transactions
  2. When specifying data_destination_config:
    • If the delivery_type is PULL, ONLY “type” field is required.
    • If the delivery_type is PUSH, BOTH “type” and “webhook_url” fields are required.

Authorizations

​
X-API-KEY
string
header
required

Body

application/json
​
filter_id
string<uuid>
required
​
data_source_config
object
required
​
data_destination_config
object
required
​
description
string | null

Response

Successful Response

​
filter_id
string<uuid>
required
​
data_source_config
object
required
​
data_destination_config
object
required
​
id
string<uuid> | null
​
description
string | null
​
external_workflow_id
string | null