Flow blocks

Every flow block the server knows is available as a typed function: blocks.<family>.<name>(...). A trailing underscore avoids Python keywords: blocks.control.if_, blocks.error.raise_, blocks.response.return_. The functions are generated from the server’s own block registry, so each lists every option with its default, limits and allowed values in its docstring (help(blocks.resource.list)), and the catalogue always matches the server.

from pawabase_iac import blocks

blocks.resource.list(resource="orders", filters={"status": "paid"}, limit=50)
blocks.mail.send(to="{{ steps.load.output.email }}", template="receipt")
blocks.control.retry(attempts=3, base_delay=2)

The families

Family	Blocks
ai (7)	`agent`, `answer`, `chat`, `embed`, `knowledge_add`, `knowledge_search`, `search`
trigger (8)	`event`, `http`, `job`, `manual`, `realtime`, `resource`, `schedule`, `webhook`
resource (5)	`create`, `delete`, `get`, `list`, `update`
control (11)	`delay`, `foreach`, `if_`, `merge`, `noop`, `retry`, `set`, `stop`, `switch`, `timeout`, `while_`
transform (12)	`batch`, `filter`, `flatten`, `group`, `map`, `pick`, `rename`, `slice`, `sort`, `summarize`, `template`, `unique`
storage (4)	`delete`, `put`, `read`, `signed_url`
cache (4)	`delete`, `get`, `invalidate`, `set`
auth (3)	`lookup`, `require`, `user`
db (2)	`query`, `transaction`
json (2)	`parse`, `stringify`
error / event / flow / http / log / mail / math / metric / policy / queue / realtime / response / secret / time / util / validate / webhook / crypto (1 each)	`error.raise_`, `event.emit`, `flow.call`, `http.request`, `log.write`, `mail.send`, `math.calculate`, `metric.increment`, `policy.check`, `queue.flow`, `realtime.publish`, `response.return_`, `secret.get`, `time.now`, `util.id`, `validate.schema`, `webhook.send`, `crypto.hash`

Common blocks

Block	Use it to
`trigger.http`	Start from a request. `method`, `path`, `policy`
`trigger.event`	Start when an event fires
`trigger.schedule`	Start on a cron or interval
`resource.get/list/create/update/delete`	Read and write your tables
`control.if_`	Branch with a `P` condition (handles `true`, `false`)
`control.switch`	Branch on a value to several handles
`control.foreach`	Loop over a list (handles `item`, `done`)
`control.retry`	Retry a step with backoff
`mail.send`	Send an email (`to`, `template`, `data`, or `subject`/`text`/`html`)
`queue.flow`	Run another flow in the background (`flow`, `input`, `queue`, `delay`)
`event.emit`	Publish an event
`realtime.publish`	Push a message to a channel
`http.request`	Call another API (`method`, `url`, `headers`, `body`, `retries`)
`response.return_`	Send the flow’s response (`status`, `body`)
`error.raise_`	Stop with an error response (`status`, `message`)
`validate.schema`	Check the input against a shape

Most blocks also give you an error handle for the failure path.

Naming blocks

Always .named("id") the blocks you reference later: ctx.steps.<id>.output. Unnamed blocks get generated ids that change when the graph does.

Regenerating the catalogue

When the server gains blocks, regenerate the functions from its registry (this is a maintainer task; see the package’s README). The count is 69 blocks in 27 families at the time of writing.

Flows

Link blocks into a graph.

Flow editor

The same in Studio.

Overview

Infrastructure as code

Define your backend

Logic and events

Files and mail

Ship it

Reference

SDK clients

The families

Common blocks

Naming blocks

Regenerating the catalogue

Flows

Flow editor

​The families

​Common blocks

​Naming blocks

​Regenerating the catalogue

Flows

Flow editor

The families

Common blocks

Naming blocks

Regenerating the catalogue