SAI360 GRC × Ambacti

Bring SAI360 GRC into
the flow of work.

A little less busywork with SAI360 GRC.

Roman aqueduct developing from a precise architectural drawing into marble.
Gather contextDo the workReview & share
Table Record6 capabilities
  • Get table records as JSON

    Retrieve table records in JSON format

  • Get table records as XML

    Retrieve table records in XML or ZIP format

  • Map fields for JSON

    Map input fields to SAI360 table attributes for JSON output

  • Query or delete records

    Query records via POST and then GET XML or DELETE them

  • Save table records from JSON

    Create or update table records using JSON format

  • Save table records from XML

    Create or update table records using XML format

Datastore2 capabilities
  • Prime for execution

    Prime datastore for execution (paginated)

  • Direct execute

    Directly execute datastore query and retrieve results

Session3 capabilities
  • Logout
  • Retrieve log
  • Get version info
GraphQL1 capabilities
  • Execute a graph ql query

    Execute a GraphQL query against the SAI360 API

Frequently asked
questions.

What could an Ambacti integration do with SAI360 GRC?

The documented operations include Table Record: Get table records as JSON; Table Record: Get table records as XML; Table Record: Map fields for JSON; Table Record: Query or delete records.

Could I keep a workflow read-only?

For a read-only workflow, limit account permissions to reading data and exclude actions that create, update, or delete records.

Will every action run automatically?

Choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.

Do I need to review actions in SAI360 GRC?

Decide which work could run on its own and which steps need your review.