Integration
Connect Picreel to Browser Use
When something happens in Picreel, your agent does the next thing in Browser Use. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Picreel and Browser Use to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Picreel and Browser Use
Triggers and actions 1 trigger · 7 actions
Trigger
New leadFires instantly when Picreel captures a new lead. Manual-registration webhook: in Picreel, click Leads in the left sidebar, click Export to CRMs and choose Webhooks, paste this trigger's minted URL into the URL field at the top, tick "Live export after submit", and save. The payload arrives flat and binds as {{ trigger.body.* }} — email, name, phone, request_url, user_id.
Action
Delete profileDelete a browser profile.
- Delete workspace
Delete a workspace.
- Get profile
Get the details of a specific browser profile.
- Get workspace
Get the details of a specific workspace.
- List workspace files
List files stored in a workspace.
- Update profile
Update a browser profile.
- Upload workspace files
Upload files into a workspace.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews