We've made some improvements to Browse AI's Zapier integration that you're going to love! Let's go from least geeky/advanced to most.
Better Handling of Data Returned from Browse Al
In the previous version of our Zapier integration, there was a parent object called taskJob and within that we provided the extra data. This added one extra level that we deemed unnecessary, so we changed it!
Before
There was only ever one task provided in the data so there was no need of having the parent object.
After
Now, it's gone :)
Filter Robots by Team on 'New Task' Trigger
Previously, if you were a member/owne of multiple Browse AI teams there was no way toget access to the robots beyond your Personal team. Now you can see all of your teams, and therefore all of your robots.
UX Enhancements and Terminology Updates
Our team did a lot of cleaning up that may not be evident at first glance. Here's a summary of what we did:
- The NEW version simplifies field names, reduces nesting levels, and introduces a
Statusfield. - The OLD version uses more detailed field names and a deeper hierarchical structure.
- The NEW version improves clarity by grouping input parameters and adding status and position fields for companies.
These changes in the NEW version aim to make the data more accessible and easier to parse, reducing complexity and improving the organization of related fields.
Key Differences:
- Top-Level Naming:
- OLD:
taskJob - NEW: Fields are directly named without a top-level
taskJob.
- OLD:
- Field Names:
- OLD: Uses more descriptive nested field names, e.g.,
Task Execution ID,Retried Task Execution ID. - NEW: Simplifies field names, e.g.,
Task ID,Retried Task ID.
- OLD: Uses more descriptive nested field names, e.g.,
- Status Field:
- OLD: No explicit status field.
- NEW: Includes
Statusfield with valuesuccessful.
- Nesting Level:
- OLD: Uses deeper nesting under
variablesandYC Companies. - NEW: Keeps related fields under
inputParametersbut reduces nesting forYC Companies.
- OLD: Uses deeper nesting under
- Trigger Details:
- OLD: Uses
Triggered By API,Triggered By Task Monitor ID. - NEW: Uses
Run By API,Run By Task Monitor ID.
- OLD: Uses
- Error Message:
- Both versions have an
Error Messagefield but are nested differently.
- Both versions have an
- Data Grouping:
- OLD: Groups variables under
variables. - NEW: Groups input parameters under
inputParameter.
- OLD: Groups variables under
- Captured Data URL:
- NEW: Adds
Captured Data Temporary Urlnot present in OLD.
- NEW: Adds
- Data Removed and URLs:
- Both versions handle
Video Removed AtandVideo URLsimilarly, but the NEW version includesCaptured Data Temporary Url
- Both versions handle
Using the Latest Version of Browse Al's Public API
NOTE: While this change is what allowed us to accomplish some of what is shown above, this will also be relevant to those who take advantage of Custom Actions in Zapier, where you use the authentication of the integration and then harness access to the API. The integration previously used V1 of the Browse AI API and it now uses V2.
BEFORE: V1
Tasks
GET:Retrieve list of tasks under your account
Task Execution
POST:Run a taskGET:Retrieve a task execution
Monitors
GET:Retrieve a task's monitorsPOST:Create a new monitor on a taskGET:Retrieve a task's monitorPATCH:Update a task monitorDELETE:Delete a task's monitor
Bulk Runs
POST:Bulk run a taskGET:Retrieve a task's bulk runs listGET:Retrieve a task's bulk run
With V2, users will now get access to all of the following.
AFTER: V2
System
- GET: Endpoint for checking the status of Browse AI infrastructure
Robots
- GET:
Retrieve list of robots under your account - GET:
Retrieve single robot by ID - PATCH:
Update a robot's cookies
Tasks
- GET:
Get all tasks by a robot - POST:
Run a robot - GET:
Retrieve a task
Monitors
- GET:
Retrieve a robot's monitors - POST:
Create a new monitor on a robot - GET:
Retrieve a robot's monitor - PATCH:
Update a robot's monitor - DELETE:
Delete a robot's monitor
Webhooks
- GET:
Retrieve a robot's webhooks - POST:
Create a new webhook on a robot - DELETE:
Delete a robot's webhook
Bulk Runs
- POST:
Bulk run tasks - GET:
Retrieve a robot's bulk runs list - GET:
Retrieve a robot's bulk run
That's a Wrap!
While at first glance it may not appear like much has changed, for those of you who are familiar with Zapier these will be quality-of-life improvements. Stay tuned for more resources about using Custom Actions in Zapier in order to harness the full power of the Browse AI API!
