Data & Docs ยท CONNECTIONRead and write Caspio table, view and directory records, manage fields, users, files, DataPage deployment and tasks.
Explore 89 workflow actions for Caspio, including account permissions and operation limits.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
Each field definition includes: Name (the identifier used in all queries), Type (data type), Label (optional friendly display name), Unique, and Description (optional.
A repeated request may repeat the external action. Review the previous result before retrying a write.
The request body must include at minimum the Email field.
A repeated request may repeat the external action. Review the previous result before retrying a write.
- If folderId is empty, the root folder is used as the destination.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Creates a table.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Each field definition includes: Name (the identifier used in all queries), Type (data type), Label (optional friendly display name), Unique, and Description (optional.
A repeated request may repeat the external action. Review the previous result before retrying a write.
The request body is a flat JSON object of field name/value pairs (e.g., {"Name": "John", "Age": 30}).
A repeated request may repeat the external action. Review the previous result before retrying a write.
The request body is a flat JSON object of field name/value pairs.
A repeated request may repeat the external action. Review the previous result before retrying a write.
- Maximum 1000 records per request.
A repeated request may repeat the external action. Review the previous result before retrying a write.
- Maximum 1000 records per request.
A repeated request may repeat the external action. Review the previous result before retrying a write.
- Maximum 1000 records per request.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deletes a directory field.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deletes a directory user by UserGUID.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deletes a directory-user attachment file.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deletes a file by file ID.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deletes a file by file path.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deletes a table attachment file.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deletes a table field.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deletes a table record by PK_ID.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deletes a view attachment file.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deletes a view record by PK_ID.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deletes a webhook event.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deletes an outgoing webhook and its events.
A repeated request may repeat the external action. Review the previous result before retrying a write.
This operation is irreversible.
A repeated request may repeat the external action. Review the previous result before retrying a write.
where is required.
A repeated request may repeat the external action. Review the previous result before retrying a write.
This operation is irreversible.
A repeated request may repeat the external action. Review the previous result before retrying a write.
where is required.
A repeated request may repeat the external action. Review the previous result before retrying a write.
This operation is irreversible.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deploys or undeploys a DataPage.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deploys or undeploys all DataPages in a Bridge application.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Gets a Bridge application.
Gets a data import/export task.
Gets a DataPage.
Gets a directory.
Each field includes: Name (the identifier to use in all queries), Type (data type), Label (optional friendly display name), Unique, Editable (false for auto-generated fields.
Gets a Flex application.
Gets a table.
Each field includes: Name (the identifier to use in all queries), Type (data type), Label (optional friendly display name), Unique, Editable (false for auto-generated fields.
Gets a table record by PK_ID.
Get a task.
Gets a view.
Gets a view field.
Gets a view record by PK_ID.
- messageCount, callCount, and errorCount are event activities from the last 30 days.
- messageCount, callCount, and errorCount are webhook activities from the last 30 days.
Gets attachment file metadata for multiple directory users.
Returns metadata for files stored in an Attachment-type field: PK_ID (the table record's internal ID), fileName, fileType, size, dateCreated, and lastModified.
Returns metadata for files stored in an Attachment-type field: PK_ID, fileName, fileType, size, dateCreated, and lastModified.
Returns metadata including the file's fileId (an internal GUID used for download), name, size, contentType, dateCreated, lastModified, and fullFilePath.
The file path comes from a File-type field value in a table or view record (e.g., '/photos/logo.jpg', '/report.pdf').
Gets folder metadata.
Get the code that embeds a DataPage on a page: iFrame, URL, Embedded or .NET.
Each entry contains the directory name, description and the complete list of fields.
Each entry contains the full webhook definition plus all events registered for that webhook.
Each entry contains the table name, description and the complete list of fields.
Each entry contains the view name, description and the complete list of fields.
Bridge applications are Caspio's low-code apps built from DataPages, similar to web applications.
Data import/export tasks are Caspio's configurable jobs for moving data into or out of tables, similar to ETL pipelines.
Lists DataPages in a Bridge application.
Directories are identity and authentication services that manage app user accounts.
Each field includes: Name (the identifier to use in all queries), Type (data type), Label (optional friendly display name), Unique, Editable (false for auto-generated fields.
In addition to the directory table fields, the following user attributes are returned: - _status - user status: 'Active', 'Inactive', 'ActivationPending', 'ActivationExpired'.
- eventType is an optional query parameter that filters results by event type.
- If folderId is empty, the list of files from the root folder is returned.
Flex applications are Caspio's low-code apps built from AppPages and DataParts, similar to web applications.
- If folderId is empty, the list of folders from the root folder is returned.
Outgoing webhooks are Caspio's event-triggered HTTP callbacks to external systems, similar to real-time notifications.
Each field includes: Name (the identifier to use in all queries), Type (data type), Label (optional friendly display name), Unique, Editable (false for auto-generated fields.
Supports Microsoft SQL Server WHERE syntax (LIKE, AND, OR, NOT, IN, BETWEEN, comparison operators, etc.).
Tables are Caspio's primary data storage objects (like database tables).
Tasks are Caspio's scheduled or on-demand automation jobs that run business logic - record inserts, updates and deletes, email and SMS notifications, joins, groupings and.
Each field includes: Name (the identifier to use in queries), TableFieldName (the source table and field in Table.Field format, revealing which underlying table each field comes.
The query syntax is identical to querying tables - supports Microsoft SQL Server WHERE syntax (LIKE, AND, OR, NOT, IN, BETWEEN, comparison operators, etc.).
Views are Caspio's predefined data sources that filter a single table or join multiple tables, similar to database views.
where is required.
A repeated request may repeat the external action. Review the previous result before retrying a write.
where is required.
A repeated request may repeat the external action. Review the previous result before retrying a write.
where is required.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Only the fields included in the request body are modified; unspecified fields are left unchanged.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Only the fields included in the request body are modified; unspecified fields are left unchanged.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Runs a data import/export task.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Returns files matching the specified name filter, regardless of folder hierarchy.
Returns folders matching the specified name filter, regardless of folder hierarchy.
Each field definition includes: Name (the identifier used in all queries), Type (data type), Label (optional friendly display name), Unique, and Description (optional.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Updates a directory user by UserGUID.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Each field definition includes: Name (the identifier used in all queries), Type (data type), Label (optional friendly display name), Unique, and Description (optional.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Only the fields included in the request body are modified; unspecified fields are left unchanged.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Only the fields included in the request body are modified; unspecified fields are left unchanged.
A repeated request may repeat the external action. Review the previous result before retrying a write.
- Only the fields included in the request body are modified; unspecified fields are left unchanged.
A repeated request may repeat the external action. Review the previous result before retrying a write.
- Only the fields included in the request body are modified; unspecified fields are left unchanged.
A repeated request may repeat the external action. Review the previous result before retrying a write.
- Only the fields included in the request body are modified; unspecified fields are left unchanged.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
Inspect step outputs and confirm the result in Caspio. A saved workflow is not a completed provider action.
