SeaTable × AmbactiBring SeaTable into
the flow of work.
A little less busywork with SeaTable.
Other operations5 capabilities+
- Get many rowsRead
- Get a rowRead
- Create a rowWrite
- Delete a rowWrite
- Update a rowWrite
Asset2 capabilities+
- Get the public URL from asset pathRead
- Upload a file or imageWrite
Add a file/image to an existing row
Base3 capabilities+
- Get username from email or nameRead
Get the username from the email or name of a collaborator
- Get metadata of a baseRead
Get the complete metadata of the base
- Create a snapshotWrite
Create a snapshot of the base
Link3 capabilities+
- List row linksRead
List all links of a specific row
- Add a row linkWrite
Create a link between two rows in a link column
- Remove a row linkWrite
Remove a link between two rows from a link column
Row8 capabilities+
- Get many rowsRead
Get many rows from a table or a table view
- Get a rowRead
Get the content of a row
- Search a row by keywordRead
Search one or multiple rows
- Create a rowWrite
Create a new row
- Delete a rowWrite
- Add a row lockWrite
Lock a row to prevent further changes
- Remove a row lockWrite
Remove the lock from a row
- Update a rowWrite
Update the content of a row
Update events4 capabilities+
- New RowEvent
- New SignatureEvent
- New or Updated RowEvent
- Row CreatedEvent
Frequently asked
questions.
What could an Ambacti integration do with SeaTable?
The documented operations include Get many rows; Get a row; Asset: Get the public URL from asset path; Base: Get username from email or name.
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 SeaTable?
Decide which work could run on its own and which steps need your review.