AZURE

Table Storage actions

14 actions you can wire into a flow, alongside everything else in the Azure integration.

Every Table Storage action

  • Azure Table Storage: Batch RowsApply up to 100 row changes as one all-or-nothing transaction. Every change must be in the SAME partition: that is the service's rule, not ours, and it is what makes the batch atomic
  • Azure Table Storage: Create TableCreate a table in the storage account. Optionally succeed quietly when it already exists, so a flow can create-on-first-run without an error branch
  • Azure Table Storage: Delete RowDelete one row by Partition Key and Row Key. Supply an ETag to fail if the row changed since you read it
  • Azure Table Storage: Delete TableDelete a table and every row in it. The name stays unusable for up to about 40 seconds afterwards while the service reclaims it
  • Azure Table Storage: Generate SAS LinkCreate a time-limited shared access signature for one table: hand out access without sharing the account key, optionally narrowed to a slice of rows. Signed locally with the account key; no API call is made
  • Azure Table Storage: Get Access PoliciesRead the stored access policies on a table: the named, revocable grants a SAS link can point at instead of carrying its own permissions
  • Azure Table Storage: Get RowFetch one row by Partition Key and Row Key. This is the fast path: the only lookup that goes straight to the row rather than scanning
  • Azure Table Storage: Get Service PropertiesRead the account-level Table service settings: CORS rules, logging and metrics, and optionally the geo-replication status. Diagnostic; rarely what a flow needs
  • Azure Table Storage: Insert RowInsert a new row. Fails if a row with the same Partition Key and Row Key already exists: this is the strictly-create path; use Upsert Row to insert-or-update
  • Azure Table Storage: List TablesList the tables in the storage account
  • Azure Table Storage: Query RowsQuery rows with an OData filter. Include the Partition Key in the filter wherever you can: only Partition Key and Row Key are indexed, so any other filter scans the whole table and gets slower as it grows
  • Azure Table Storage: Set Access PoliciesWrite the stored access policies on a table. This REPLACES the whole set: any policy you leave out is removed, which instantly revokes every SAS link that referenced it. Send an empty list to clear them all
  • Azure Table Storage: Update RowUpdate a row that must already exist. Merge only changes the fields you supply; Replace DELETES every field you leave out. Supply an ETag to fail if the row changed since you read it
  • Azure Table Storage: Upsert RowInsert the row, or update it if it already exists. The action most flows want. Merge only changes the fields you supply; Replace DELETES every field you leave out

Also in Azure

Put Table Storage in a flow

These actions sit on the same canvas as every other integration, so a Table Storage step can follow a form, a schedule or a message without any glue code.