šŸ“„
FilesWorkflow Docs
  • šŸ‘Welcome
    • Introduction to FilesWorkflow
    • Key features and benefits
  • šŸ§”Get Started
    • Account creation
    • Personal & Organization
    • Basic interface navigation
    • Tasks & Workflows
    • Browser-task & Server-task
    • Public & Private
    • Run task & workflow
    • Controlled Sharing
    • Creating workflows
    • Limitations
    • Official Tasks & Workflows
    • How to protect your file security
  • šŸ’»Developer
    • Creating custom tasks
    • Advanced settings for tasks
    • Task Writing Guide
    • Task examples
    • Task templates
    • Generate scripts using AI
  • šŸ’ŽPricing and Plans
    • Plan comparisons
    • Change Plan
  • ā“FAQ
  • šŸ“ƒLegal
    • Privacy Policy
    • Terms of Service
  • šŸ“’Release Note
Powered by GitBook
On this page
  1. Get Started

Browser-task & Server-task

FilesWorkflow supports two types of tasks: Browser-tasks and Server-tasks.

  1. Browser-tasks:

    • Run directly in the user's web browser.

    • Leverage browser-specific features and APIs.

    • Ideal for client-side operations like file transformations.

    • Limited by browser capabilities and security restrictions.

  2. Server-tasks:

    • Execute on cloud servers.

    • Utilize Node.js runtime (currently version 20).

    • Suitable for more complex or resource-intensive operations.

    • Can access server-side libraries and perform operations not possible in browsers.

    • Support environment variables for secure handling of sensitive information: ā€¢ Set up in task configuration. ā€¢ Injected at runtime. ā€¢ Accessible within the task code. ā€¢ Ideal for API keys, credentials, or other sensitive data.

  3. Combining Tasks:

    • Workflows can include both browser-tasks and server-tasks.

    • Allows for flexible and powerful processing pipelines.

    • Optimize performance by choosing the appropriate task type for each operation.

PreviousTasks & WorkflowsNextPublic & Private

Last updated 10 months ago

šŸ§”