Docs / Reference / act: act through connector

act: act through connector.

The installed connector, the kind, the arguments with their sources to a move, proposed or running by the grant's mode; then the source's own id for what was done

Figure 1POST /v1/act/act_through_connectorspecified

The caller sends ActThroughConnectorInput to /v1/act/act_through_connector. The platform returns a card whose body is Move.

POST/v1/act/act_through_connectora task, 202

Run a kind of action. The call needs the brand rung under a token with the act grant, and it is served by the platform.

The route takes ActThroughConnectorInput and returns a card whose body is Move.

Request body#

The request body is ActThroughConnectorInput.

field	type	required	note
`installed_connector`	`id`	yes
`kind_of_action`	`id`	yes
`arguments`	`{text:json}`	yes
`argument_sources`	`{text:text}`	yes	the record by id, a definition, a person’s own words

Response#

The route returns a card whose body is Move. Every card ends with a foot that states the basis of each number, the scope of the call, and the time when the facts were true. This route runs as a long step and returns a task with status 202. POST /v1/work/status returns the task’s progress, and POST /v1/work/cancel stops the task.

Headers#

header	required	meaning
`Scale-Scope`	yes	the scope the call runs in: tenant/, then /brand/, then /strategy/
`Scale-As-True-On`	no	the date the facts must have been true on; defaults to now
`Scale-As-Known-On`	no	the date the facts must have been known on; defaults to now
`Scale-Key`	no	for a change, the key made from the input; a repeat under the same key returns the unit held and writes nothing

A caller needs the brand rung and a token with the act grant. The platform serves this route.

Example#

The example sends the smallest body that ActThroughConnectorInput allows. The build validates it against the schema of ActThroughConnectorInput.

Example

curl -X POST https://api.scaleintelligence.co/v1/act/act_through_connector \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "installed_connector": "…", "kind_of_action": "…", "arguments": {}, "argument_sources": {} }'

import { client } from "@scale/sdk";
const answer = await client.act.act_through_connector({
    "installed_connector": "…",
    "kind_of_action": "…",
    "arguments": {},
    "argument_sources": {}
  });
// answer.body is a Move. answer.foot holds the basis, the scope and the time.

import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/act_through_connector",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "installed_connector": "…",
      "kind_of_action": "…",
      "arguments": {},
      "argument_sources": {}
    }).json()

let answer: Card = client.post("https://api.scaleintelligence.co/v1/act/act_through_connector")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&ActThroughConnectorInput { /* the fields of the page */ }).send().await?.json().await?;

MCP tool#

The MCP tool si.act.act_through_connector takes the same input and returns the same card. The tool changes data and needs a grant. An MCP host that renders cards draws this card from ui://scale-intelligence/cards/Move. The tool’s page describes it.

POST /v1/act/act_through_connector
Scale-Scope: …
Scale-As-True-On: …
Scale-As-Known-On: …
Scale-Key: …
content-type: application/json

{
  "installed_connector": "…",
  "kind_of_action": "…",
  "arguments": {},
  "argument_sources": {}
}

Without a key, this page shows the request only. The request body is ActThroughConnectorInput, and the route returns a card whose body is Move.

Claims#

claim	state	route or tool
The platform serves the route /v1/act/act_through_connector at contract 0476e35e6e275db5.	target	`/v1/act/act_through_connector`