Vacuum Table

Updates table storage in Firebolt with VACUUM.

PUT

Query

Field selectionChoose which fields should be included in the response. Learn more

string

Comma-separated response fields to include.

Body

Arguments

stringrequired

User engine host to execute the VACUUM statement against.

stringrequired

The Firebolt table or aggregating index to vacuum.

Uncommon arguments

string

Optional engine name to send as the Firebolt engine query parameter.

string

Optional Firebolt database to execute the VACUUM statement in.

string

Optional VACUUM options, for example INDEXES = NONE or MAX_CONCURRENCY = 1.

Try this request

Request

curl --request PUT \
  --url "https://connect.mindcloud.co/v1/universal/firebolt/0.0.5/actions/vacuum-table" \
  --header "Authorization: Bearer $MINDCLOUD_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "engineHost": "",
  "tableName": ""
}'

{
  "success": true,
  "data": [
    {
      "message": "string",
      "monitorSql": "string",
      "token": "string"
    }
  ],
  "meta": {}
}

Every app you connect,one REST pattern

Call any app with one REST pattern. MindCloud handles each provider's auth, request shape, and responses for you.

Learn what the Universal API is

One REST patternUse the same request structure across apps like Slack, HubSpot, Salesforce, and thousands more.

Managed connectionsSend a MindCloud connection ID instead of handling provider tokens, refresh logic, and credential storage yourself.

Action-level docsEach action page shows the exact endpoint, required arguments, optional controls, and response behavior for that app version.