Record captured software issues in central document tables

When a new issue is captured in Browserless, automatically add a record to the centralized bug database in LogiONE Document.

Try:

See all LogiONE Document + Browserless integrations or talk to a human

Trusted by teams already building on Knit·

4.9/5 on G2·

Google for Startups Accelerator

How Knit builds this workflow

The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.

LogiONE Document Explore LogiONE Document →

Triggers

New page created

Fires when a new page or doc is created in LogiONE Document.

Record added

Fires when a new record is added to a database or table in LogiONE Document.

Doc published

Fires when a doc in LogiONE Document is published or shared.

Status changed

Fires when a status field changes on a record in LogiONE Document.

Actions

Create page from template

Starts a new page in LogiONE Document from a saved template.

Add or update record

Creates or updates a record in LogiONE Document.

Append text

Adds text to the end of an existing doc in LogiONE Document.

Move page

Moves a page in LogiONE Document into a different space.

Browserless Explore Browserless →

Triggers

New issue captured

Fires when a new error or issue is captured in Browserless.

Issue status changed

Fires when an issue's status changes in Browserless.

Deployment tracked

Fires when a new deployment is tracked in Browserless.

Actions

Create issue

Creates or updates an issue in Browserless.

Assign issue

Assigns an issue in Browserless to a teammate.

Resolve issue

Resolves or mutes an issue in Browserless.

Document tracked software deployments in wiki pages When a deployment is tracked in Browserless, automatically append release details to the corresponding product page in LogiONE Document. See details

Log developer issues from document status changes When a specification document status changes in LogiONE Document, automatically create an issue in Browserless so engineers can start development. See details

See all LogiONE Document + Browserless integrations → · Browse the full workflow library →

Enterprise-grade security

Visit our Security Center Review the DPA

FAQ

Common questions

Can Knit build “Record captured software issues in central document tables” between LogiONE Document and Browserless?

Yes — describe it in the box above and Knit's Integrations Agent researches LogiONE Document and Browserless's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.

How long does it take to build?

Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.

Why connect development platforms in Browserless to document tools in LogiONE Document?

It automatically keeps release records and bug tables updated in LogiONE Document while letting documentation status changes in LogiONE Document generate software issues in Browserless.

Can deployment updates in Browserless update team documentation in LogiONE Document?

Yes, whenever a deployment is tracked in Browserless, release details can automatically append text to release documentation pages in LogiONE Document.