Save an action | CloudRaker documentation

Saves a reusable, named configuration for a capability so calls stop repeating themselves.

Pass a saved action to any run as action: "<id or slug>". Inline config on the call is deep-merged over the saved config, and inline wins — so one saved action can be nudged per call without being redefined.

1 {
2   "capability": "extract",
3   "name": "W-9 basics",
4   "config": {
5     "schema": {
6       "type": "object",
7       "properties": {
8         "business_name": { "type": ["string", "null"] },
9         "tax_classification": { "type": ["string", "null"] }
10       }
11     }
12   }
13 }

Saved actions are also what governance, record-type binding and stable configuration under keep hang off. Check the catalog for the config schema of the capability you are saving.

Learn more: Pipeline guide

Deprecated: saved actions are becoming per-capability configs — use POST/GET/PATCH/DELETE /v1/{capability}/configs instead (/v1/extract/configs, /v1/redact/configs, /v1/fill/configs). Signing keeps using POST /v1/sign.

Saves a reusable, named configuration for a capability so calls stop repeating themselves. Pass a saved action to any run as `action: "<id or slug>"`. Inline config on the call is deep-merged over the saved config, and inline wins — so one saved action can be nudged per call without being redefined. ```json { "capability": "extract", "name": "W-9 basics", "config": { "schema": { "type": "object", "properties": { "business_name": { "type": ["string", "null"] }, "tax_classification": { "type": ["string", "null"] } } } } } ``` Saved actions are also what governance, record-type binding and stable configuration under [keep](https://docs.cloudraker.com/api/cloud-raker-api/runs/keep-run) hang off. Check [the catalog](https://docs.cloudraker.com/api/cloud-raker-api/actions/list-capabilities) for the config schema of the capability you are saving. **Learn more:** [Pipeline guide](https://docs.cloudraker.com/capabilities/pipeline) **Deprecated:** saved actions are becoming per-capability configs — use `POST/GET/PATCH/DELETE /v1/{capability}/configs` instead (`/v1/extract/configs`, `/v1/redact/configs`, `/v1/fill/configs`). Signing keeps using `POST /v1/sign`.

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Request

This endpoint expects an object.

capabilityenumRequired

namestringRequired1-200 characters

configmap from strings to anyOptional

mimeTypestringOptional>=1 character

Response

The saved action.

object"action"

idstring

slugstring

namestring

capabilityenum

configmap from strings to any

Errors

400

Bad Request Error

429

Too Many Requests Error

Saves a reusable, named configuration for a capability so calls stop repeating themselves.

1 {
2   "capability": "extract",
3   "name": "W-9 basics",
4   "config": {
5     "schema": {
6       "type": "object",
7       "properties": {
8         "business_name": { "type": ["string", "null"] },
9         "tax_classification": { "type": ["string", "null"] }
10       }
11     }
12   }
13 }

Saved actions are also what governance, record-type binding and stable configuration under keep hang off. Check the catalog for the config schema of the capability you are saving.

Learn more: Pipeline guide

$	curl -X POST https://api.cloudraker.com/v1/actions \
>	-H "Authorization: Bearer <token>" \
>	-H "Content-Type: application/json" \
>	-d '{
>	"capability": "extract",
>	"name": "Medical intake"
>	}'

1	{
2	"object": "string",
3	"id": "string",
4	"slug": "string",
5	"name": "string",
6	"capability": "extract",
7	"config": {}
8	}

1	{
2	"capability": "extract",
3	"name": "W-9 basics",
4	"config": {
5	"schema": {
6	"type": "object",
7	"properties": {
8	"business_name": { "type": ["string", "null"] },
9	"tax_classification": { "type": ["string", "null"] }
10	}
11	}
12	}
13	}