← Back to connectors

Browserlify connector for Okou

Connect to a public HTTPS Browserlify instance to render web pages as PDFs, screenshots, text, or HTML and inspect browser sessions.

Data & infrastructure · Public HTTPS instance host

Use Browserlify in Okou

Use Browserlify or a self-hosted Browserlify browser service to render web pages as PDFs or screenshots, extract rendered text or HTML, and inspect active browser sessions.

Once connected, supported Browserlify actions can become steps in a reusable workflow alongside the other services your team uses. Run the workflow once, on a schedule, or when an event starts it.

What you can do with Browserlify

  • Read Browserlify's active headless-session metadata and an existing session screenshot.
  • Render a user-requested page as PDF, image, text, or HTML through Browserlify.

How the Browserlify connector works

A connected service becomes one permissioned step in the work you hand off.

  1. 1

    Connect Browserlify

    Choose Public HTTPS instance host.

  2. 2

    Choose the work

    Use only the supported actions your workflow needs.

  3. 3

    Run it your way

    Start it once, schedule it, or attach an event trigger.

Connect Browserlify securely

Use the connection method that fits your account and grant only the access the workflow needs.

  • Public HTTPS instance host

Connector access is controlled per service and per action, so a workflow does not need broader access than the work you ask it to do.

What Browserlify covers

The topics this connector's published operations touch.

  • browser automation
  • headless chrome
  • web scraping
  • screenshots
  • pdf
  • self hosted

Browserlify connector questions

What can Okou do with Browserlify?
Connect to a public HTTPS Browserlify instance to render web pages as PDFs, screenshots, text, or HTML and inspect browser sessions. Documented actions include: Read Browserlify's active headless-session metadata and an existing session screenshot. Render a user-requested page as PDF, image, text, or HTML through Browserlify.
How do I connect Browserlify to Okou?
Connect Browserlify using Public HTTPS instance host. The connection controls which supported actions a workflow can use.
Can Browserlify run in an automated workflow?
Yes. After it is connected, supported Browserlify actions can run in reusable Okou workflows on demand, on a schedule, or from an event trigger.

More data & infrastructure connectors

Explore other connectors in the same product category.