OpenFn / OpenFn/lightning

Improve Tool Discovery and Canvas Usability for First Time users

Open
#4,194 0 comments 0 reactions 1 assignee View on GitHub

@jackohilts is already working on this.

Since Dec 12, 2025.

Epic
Dominant language
Elixir
Stars
296
Forks
86
Avg merge
1d 13h
Merged PRs (30d)
50

Description

Edit details of this in Google Doc here: https://docs.google.com/document/d/1p3FeHmNofYUANUDZjsECqvnR6dVGPBP7Oi2nTcWmFEI/edit?tab=t.0#heading=h.7x0zxe8odvz0

Improve Tool Discovery and Canvas Usability for First Time users

Design question: how might we make it easier for first time users to ‘get what they want’ from the canvas’?

Problem Statement: Current terminology and organization in the OpenFn canvas creates significant friction for first-time users trying to build functional workflows. Unclear naming conventions (e.g., "OpenFn Common") and limited search capabilities make it difficult for users to discover and utilize available tools effectively.

Strategic Goal: Reduce time-to-first-successful-workflow and decrease onboarding support needs by improving discoverability and offering clearer terminology.

Core user story: As a first time user of the canvas, I want the naming conventions and organisation of the ‘things I can do’ in a workflow to be easier to understand, so that I can more easily build a complete workflow which actually works

Things to consider within the scope of this Epic:

  • Renaming ‘Adaptors’ to ‘Tools’ which, in turn, contains:
    -- Adaptors (for connecting to external systems)
    -- Transformers (for ‘doing things’ during the workflow)
    -- Agents (for integrating with LLMs - usually using plain text?)
  • Updating the search bar to ‘look for’ several parameters beyond just name including:
    -- Adaptor Name
    -- Function Name (ie, surface all ‘Tools’ that contain a certain function when I input it
    -- ‘Tags’ (Search terms that we can configure, eg for
  • Renaming ‘Common’ to ‘JavaScript Code’
    -- Include different ‘Tags’ for users to find this including Transformer; JS; Code; Custom; Logic; OpenFn; Common

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.