Plugins Overview

Plugins are the workflow building blocks Tensorify uses to render node behavior in the app.

Current public framing

For the current MVP, the public docs should frame plugins as:

  • built-in or internally managed building blocks
  • the pieces users assemble into workflows
  • part of the app + local execution loop

The public docs should not frame plugins as a fully mature public publishing ecosystem yet.

Practical plugin categories

Examples that fit the current product story:

  • webhook triggers
  • HTTP request/API call nodes
  • transform nodes
  • conditional logic nodes
  • notification nodes

What users do with plugins today

  1. add nodes to a workflow in the editor
  2. configure settings on the node
  3. connect nodes with edges
  4. run and test the workflow locally

Good early plugin examples

For the current landing-page/user story, focus on plugins used in flows like:

  • Stripe webhook trigger
  • verify webhook payload
  • load customer/order context
  • conditional branching
  • Slack notification
  • HTTP request to internal systems

Current maturity note

Public plugin publishing is not the main MVP story yet. The public site and docs should stay conservative about promising that workflow until the SDK and publishing pipeline are more settled.