Testing
Using a test server to dry-run integrations
There are a number of ways to extract data from Agilebase, whether manually for an individual’s use or programatically for integration with other systems.
There are also multiple ways other than the user interface to enter data into Agilebase.
Users are able to:
Third parties can access data via an API, either:
There is also dedicated facility for integrating data with a Calendar
Finally, data can be sent to third party reporting tools like Power BI, Tableau, Excel or anything which can use ODBC
Users are able to add data:
Third parties can save data into agilebase:
The most recent API actions and any errors which may have occurred will be shown
Sometimes it can be useful to see the internal ID (primary key value) of each record the API acts on, to match up with info from the third party system you’re integrating with. To do this, see Accessing additional debugging information
Using a test server to dry-run integrations
Sending data to an external tool via a database link
A powerful automation feature that can allow a third party system to POST data in to Agilebase.
A powerful automation feature that can send data to third party systems.
Control how third party systems read data from Agilebase
A worked example to send Agilebase data to a third party text messaging service using Zapier
A more complex API example showing a real world integration consisting of multiple steps
Allows comments posted in Agilebase to be shared as Slack/Teams/Google etc. notifications
The data in each view can be exported when the requisite privileges are granted
Adding to or updating existing data in a table using a spreadsheet import
Logging in as a user
Creating a user account in a multi-tenanted system with an API request
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.