Anchor Browser and Kit automations

Anchor Browser reports when a task or session ends, and Kit tags a subscriber through “Add Tag to Subscriber”.

Set up an automation: when a task fails in Anchor Browser, add tag to subscriber in Kit

Build it

Or have an AI agent work across Anchor Browser and Kit: it decides what to do in each on every run, on a schedule or when you ask it in its chat.

Anchor Browser and Kit in practice

Used for

Anchor Browser reports when a task or session ends, and Kit tags a subscriber through “Add Tag to Subscriber”.

Best template

“When a task fails” in Anchor Browser, then “Add Tag to Subscriber” in Kit. A failed task is the event worth marking, and the action tags a specific Kit subscriber.

Watch out

Anchor Browser events describe tasks, not people, so decide how “Add Tag to Subscriber” finds the subscriber.

Anchor Browser and Kit templates

Pick one and Captain builds it with you.

  • When a task fails in Anchor Browser, add tag to subscriber in Kit

    Build this
  • When a browser session is ready in Anchor Browser, add tag to subscriber in Kit

    Build this
  • When a browser session is completed in Anchor Browser, add tag to subscriber in Kit

    Build this
  • When a browser session recording is ready in Anchor Browser, add tag to subscriber in Kit

    Build this
  • When a task is completed successfully in Anchor Browser, add tag to subscriber in Kit

    Build this
  • When a task is cancelled in Anchor Browser, add tag to subscriber in Kit

    Build this

Anchor Browser and Kit triggers and actions

Every one of both apps. A trigger starts the work; actions are the steps.

Triggers

6
  • When a task is completed successfullyRuns the workflow automatically whenever any task is completed successfully.
  • When a task failsRuns the workflow automatically whenever a task fails in Anchor Browser.
  • When a task is cancelledRuns the workflow automatically whenever a task is cancelled in Anchor Browser.
  • When a browser session is completedRuns the workflow automatically whenever any browser session is completed.
  • When a browser session recording is readyRuns the workflow automatically whenever a browser session recording becomes ready.

Actions

15
  • Perform web taskLaunch a secure cloud Chromium session and execute automated browsing instructions.
  • Check task generation statusRetrieve the generation status of a browser automation task.
  • Get task run statusGet the current status and result of a task run.
  • Start Browser sessionRetrieve the current generation status of a browser automation task.
  • End all Browser sessionsEnd all browser sessions to stop running automations and free their resources.

Questions about Anchor Browser and Kit

What can start a Anchor Browser and Kit automation?

“When a task fails”, “When a browser session is ready”, “When a browser session is completed”, “When a browser session recording is ready” and “When a task is completed successfully”, and the others in the templates above.

Which other apps work with both Anchor Browser and Kit?

Shopify, Slack, Zoho CRM, ThriveCart and inflow-inventory. Each one has templates with Anchor Browser and with Kit, so a third app can join the same job.

All Anchor Browser integrations · All Kit integrations · Every app, A to Z

Connect Anchor Browser and Kit

Or pick another template above. Free to start.

Build it with Captain
Anchor Browser and KitBuild it