Skip to content
finn.
Integrations Wiki.js

Integration · Knowledge and documents

Wiki.js + Finn.

Wiki.js integration with Finn. Wiki.js is an open-source wiki for publishing and organizing team documentation.

Discuss this integration Explore the workflows

The work behind the connection

What you can do with Wiki.js.

Wiki.js is an open-source wiki for publishing and organizing team documentation.

Keep operating instructions aligned with completed changes

Finn updates a team's Wiki.js runbook after a confirmed system change and carries the documentation handoff through completion.

Typically handled byOperations technical writer

Starts when

A change owner marks a system change complete in the connected engineering tool.

What Finn handles

  1. Read the final change record and relevant Wiki.js pages, compare the old instructions with the confirmed operating behavior, and collect missing details from the system owner.
  2. Revise the affected pages with concrete steps and source links, then obtain the page owner's acceptance of the operating instructions.
  3. Publish the accepted revisions under the existing page rules, notify the operations team through connected messaging, and close the documentation task with the final page links.

The result

The operating team receives current accepted instructions and the change record includes the completed documentation handoff.

Turn an expert's answer into reusable team knowledge

Finn captures a verified specialist answer, fits it into the existing wiki, and completes the response to the person who needed it.

Typically handled byTechnical knowledge coordinator

Starts when

A specialist resolves a question that is missing from the team's Wiki.js documentation.

What Finn handles

  1. Read the confirmed answer and related wiki pages, collect the examples and limits needed to make it reusable, and remove information outside the intended audience.
  2. Create or revise the relevant Wiki.js page, link the supporting material, and collect the subject owner's publication decision.
  3. Publish the accepted page, send the requester the answer and final link through connected messaging, and record the resolved question in the connected service or project tool.

The result

The original question is answered and the team gains an accepted reusable page linked to the resolution.

Complete the documentation side of a release

Finn translates a confirmed release into the wiki pages and internal communication that keep users and support teams working from the same instructions.

Typically handled byRelease documentation coordinator

Starts when

Engineering confirms a release is available in the connected issue tracker.

What Finn handles

  1. Read the shipped work and existing Wiki.js guides, identify changed user tasks, and distinguish released behavior from work that remains unfinished.
  2. Write the release explanation and revise affected instructions, using examples based on the release owner's evidence and collecting the document owner's review.
  3. Publish the accepted pages, deliver the internal release notice through connected email or chat, and attach the final documentation links to the release record.

The result

The release has current instructions and a delivered internal handoff tied to the features actually shipped.

Resolve a routine service request using the team wiki

Finn applies the instructions in Wiki.js through the real service workflow, so the employee gets a completed result rather than a page to interpret alone.

Typically handled byInternal operations service coordinator

Starts when

An employee asks for a routine service covered by the team's wiki.

What Finn handles

  1. Find the accessible Wiki.js procedure, collect the request details through connected messaging, and open the request in the connected service system.
  2. Follow the procedure's decision points, obtain any required owner approval, and perform the permitted booking or administration action through the connected service tool.
  3. Confirm the actual result, send the employee the completion details and useful instructions, and close the service record with the source page and action evidence.

The result

The request is fulfilled and the service record shows the guidance and actual result used to resolve it.

Complete a focused wiki review

Finn takes a defined set of Wiki.js pages through owner review and accepted corrections, leaving a clear record of what is current.

Typically handled byDocumentation maintenance coordinator

Starts when

A team schedules a review of a defined wiki topic or page set.

What Finn handles

  1. Read the selected pages and their linked source records, identify stale instructions or unresolved ownership, and ask the responsible owners for specific confirmations.
  2. Apply the owners' accepted corrections and repair the affected content links, preserving existing page access and recording questions the owners have not settled.
  3. Publish the accepted revisions, send the team the material changes through connected messaging, and close the connected review tasks with final links and owner decisions.

The result

The reviewed pages have current owner decisions and accepted corrections, with the maintenance work recorded as complete.

Deliver an engineering project handover

Finn assembles a useful Wiki.js handover from the final project records and transfers remaining work to the people operating the result.

Typically handled byEngineering delivery coordinator

Starts when

A project owner accepts the final technical deliverables.

What Finn handles

  1. Gather the accepted scope, architecture explanation, operating instructions, and known limitations from Wiki.js and the connected project and document tools.
  2. Create the handover page with final file links and remaining obligations, then collect the receiving team's acceptance and resolve missing documentation.
  3. Publish the accepted handover, create the remaining tasks in the connected issue tracker, and notify the receiving team with the final page and assigned work.

The result

The receiving team has an accepted handover and ownership of remaining work, linked to the final project files.

Connection setup

Set up the connection around your work.

Contact Finn to discuss the records your workflow needs and the actions you want it to perform.

Your team chooses what Finn can access, what agents can change, and when a person must approve the work. The connection needs the appropriate account access and permissions from Wiki.js.

The Finn platform

Finn Agents

Help customers. Work with your team. Finish the job.

Explore Agents

Finn Systems

Business apps for the work behind the conversation.

Explore Systems

Finn AI Gateway

Control connected AI apps, models, access, and spending.

Explore AI Gateway

Meet Finn

Put your Wiki.js integration to work.

Tell us which records, actions, and teams the connection needs to support.

Discuss your workflow Get started