Documentation and How-Tos

Documentation and tutorials on our services

About BioWorkflows

Our mission is to deliver top-tier workflows for biomedical data analysis by valuing the efforts of authors who invest their time in crafting, updating, and supporting their workflows. We offer an extensive collection of both public and premium workflows for biomedical data analysis.

Within this repository, users have the freedom to

  • Explore an array of publicly available workflows and code snippets,
  • Purchase premium workflows, and 
  • Access fee-based services provided by field experts and workflow authors.

Simultaneously, workflow creators and maintainers have the opportunity to receive compensation by offering premium workflows and/or providing paid support to users.

A workflow encompasses a wide spectrum of processes, scripts, software, or pipelines designed for the examination of biomedical data across various computational settings.

Typical categories of workflows include:

  1. Reproducible multi-step workflows: These utilize specialized workflow languages such as Nextflow and are considered "workflows" in the strictest sense.

  2. Scripts for data analysis and figure generation: Often used in the context of preparing research publications.

  3. Protocols for systematic data analysis: Developed to facilitate the methodical examination of specific data types.

  4. Tutorials: These provide guidance on the usage of particular tools or the execution of analyses for specific data types.

  5. Commercial workflows: Examples include cloud-based workflows offered by companies like Illumina through platforms like BaseSpace.

In general, any type of document that aids in the analysis of biomedical data can be uploaded (and potentially sold) as a workflow.

We serve as both a registry for external workflows and a repository for on-site workflows.

In addition to basic metadata such as title and description, workflows can incorporate optional elements like a main document, banner images, and supplementary attachments. Workflows with a "main document" stored on are termed "on-site workflows," whereas those that direct users to external webpages are known as "external workflows."

Each workflow has a primary author and the option to have one or more maintainers. While most workflows are both created and maintained by their respective authors (and maintainers), there are cases where workflows are made available as public workflows under the pseudonymous user "public." These public workflows can originate from the following sources:

  1. They may be suggested by anonymous users through the Suggest a workflow feature. These submissions undergo screening and approval by our administrative staff before being published as public workflows.

  2. Some workflows are contributed by regular users who choose to publish their workflows as public.

  3. Others are collected by our staff or automated processes.

Public workflows are accessible to everyone, even during their draft status. In this state, anyone can propose changes to the workflows, or even become a maintainer or author of the workflow

While most of our workflows are freely accessible, some are categorized as premium content.

You have the option to access these premium workflows through either individual per-workflow purchases or by subscribing to our Pro membership, which provides free access to a majority of premium workflows. Until you gain full access to these workflows, you won't have access to the attachments, and you will typically see a limited version of the main document (e.g., with source code masked).

Paid support services are available for both free and premium workflows.

Unlike other freelancing platforms like Upwork, where sellers can offer a wide range of arbitrary services, BioWorkflows distinguishes itself by anchoring services to specific workflows. These services primarily revolve around technical support for deploying and customizing existing workflows. In essence, prospective service providers are required to showcase their expertise by publishing or co-publishing (as a maintainer) an exemplary workflow. This demonstration usually include details about the type of data, operations involved, and sample output, effectively highlighting the provider's skill set. The workflows, whether free or premium, can be housed under users' or others' accounts, even as public workflows, with the service provider being the author or maintainer of these workflows.

While BioWorkflows emphasizes workflow-related services, the negotiation of exact terms between sellers and buyers provides some flexibility. This allows services to extend beyond specific workflows, offering a dynamic range of possibilities tailored to the unique needs of each service request.

Exploring and Leveraging Our Platform is meticulously crafted to facilitate the seamless exploration of workflows for your specific needs. We offer a spectrum of features designed to enhance your workflow exploration experience:

  1. Browse Published Workflows: Peruse an extensive list of workflows that have been published and are readily available for your use.
  2. Discover Public Drafts: Uncover public drafts—workflows contributed by anonymous users. These workflows are in draft status and open for your valuable input to improve them before publication (c.f., become a maintainer).
  3. Search workflows: Utilize our search functionality to locate workflows based on keywords, titles, descriptions, full-text searches, and even filter them by their support status, providing you with a powerful tool to find precisely what you need.
  4. Bookmark and Explore: Bookmark workflows of interest and revisit them conveniently whenever you need.
  5. Explore via Keywords: Navigate through related workflows by utilizing keywords that are linked to similar themes, operations, and tools. A simple click on any keyword from the information panel leads you to the related workflows.
  6. Engage Through Comments: Share your experiences and insights with the workflow community by leaving comments and feedback.
  7. Rate with Comments: Express your evaluation of workflows you've purchased by assigning ratings and providing comments to help others make informed choices.

With these features, empowers you to explore, collaborate, and make the most of the workflows tailored to your unique requirements.

Keywords, often referred to as tags, serve as invaluable markers associated with workflows, code snippets, forum topics, and users within our platform. These keywords are categorized into Topic, Operation, Data, Tool, Format, Input, and Output and are clearly defined with descriptions, metadata, and references.  They can be used for:

  • Workflow Tagging: Workflows are tagged with a diverse array of keywords, providing a nuanced description of various facets within the workflows.
  • Code Snippets Tagging: Code snippets are associated with tags corresponding to the tools utilized in the code, allowing snippets to be organized by tools used.
  • Forum Topic and Question Tagging: Questions and topics in our discussion forums are tagged with diverse keywords, enabling visitors to comprehend the essence of the discussions at a glance.
  • User Expertise Tagging: Users can showcase their expertise by listing multiple keywords in their profiles, presenting a comprehensive snapshot of their skill set.

Keywords provide an efficient way for users to locate specific content related to their interests. To check how a tag has been used, simply click a keyword and then the  (workflows) ,  (code snippets),  (discussion topics), and   (user expertise) icons on the bottom. In addition, expertise for users allow them to be notified with the publication of relevant workflows and discussions. They also allow sellers to be idenfiied through their expertise.

At, we maintain an extensive collection of tags, and users have the flexibility to add new tags. This can be done through the Explore Expertise page in the Service section, or when entering keywords for workflows or topics. This collaborative approach enhances the richness and diversity of content on our platform.

Code snippets are excerpts of source code extracted from workflows. They serve as valuable tools for showcasing the techniques employed by the workflows and the utilization of specific tools within these workflow processes. Most code snippets are linked to tags associated with these tools, creating a valuable resource for illustrating the practical application of these tools in real-world scenarios.

To access all code snippets from various workflows, you can select code snippets. You have the option to filter these code snippets by workflow languages or search for snippets containing specific keywords.

For a comprehensive list of code snippets associated with a particular tag, simply click on the tag of interest and then the   (code snippets) icon.

While you can search for workflows using keywords, topics, descriptions, and more, you may still find cases where you don't exactly locate what you need. In such situations, you have several options:

  1. Identify users with relevant expertise and review the workflows they support. You can then post a question within the context of one of these workflows. The seller may assist you in finding the right workflows or even customizing one to suit your requirements.
  2. If you have a more general question or are unsure about whom to contact, consider posting a question on our discussion forum, To maximize the quality of responses:
    • Provide detailed information about your question, including specific data types, running environments, requirements, and other relevant details. This helps other users understand your needs and provide more accurate assistance.
    • Ensure to tag your topic with appropriate tags. This practice helps us route your query to users with expertise in the related field, enhancing the likelihood of receiving valuable insights.
    • You can also opt to set up a bounty for your topic. Offering a bounty provides an incentive for other users to contribute answers to your question, increasing the chances of obtaining helpful solutions.

Pro users enjoy the benefit of permanent private storage and the ability to share unpublished workflows with others. This feature is particularly valuable for collaborating with colleagues and clients, making it especially useful for researchers and freelancers. In addition, Pro users gain unrestricted access to the majority of premium workflows, with significant discounts on other purchases. Furthermore, Pro members receive enhanced and more prompt technical support.

To become a Pro member, a monthly fee is typically required. However, you have the opportunity to earn credits through various activities on BioWorkflows, which can be applied towards your membership fees. These credit-earning activities encompass a range of contributions, including but not limited to enhancing or creating public workflows and actively participating in discussion forums.

Users who purchase "seats" within a team plan have the capability to create a dedicated team, fostering a collaborative environment where team members can readily share workflows.

Within this team setting:

  1. Team members can engage in private discussions via a team-specific discussion forum, allowing for secure and confidential communication.
  2. A team plan empowers the team leader to acquire workflows with a "volume license," enabling their use by all team members.
  3. Teams can be configured to grant team leaders control over workflow publication, receipt of income from workflow and service sales, and responsibility for covering the expenses of team members.

In essence, a team plan serves as a valuable tool for teams or organizations seeking to enhance collaboration and efficiently share their activities on

A private knowledge base is essentially a repository of archived workflows stored within your personal account or a team account. It transforms into a private knowledge base when you:

  1. Upload scripts and reports related to your completed projects as private workflows.
  2. Highlight essential project steps by including them as code snippets within the workflows.
  3. Apply keywords to categorize the workflows.

The combination of these elements—keywords, code snippets, scripts, and reports—forms a private knowledge base that you can conveniently explore and search. This private knowledge base exists within the broader public knowledge base for biomedical workflows, providing you with a secure and organized space to manage your work.

Buying Workflows and Services

When you acquire a premium workflow with a regular price, it is for your exclusive use, and you are not permitted to share it with others through any means.

However, if you have a Team membership, you have the option to purchase workflows at a Volume Price, allowing you to share these workflows with your team members, regardless of the team's size. The workflow is associated with you and all your teams, ensuring that any new members automatically gain access to these workflows. Consequently, it is advisable for team leaders, rather than regular team members, to purchase workflows, as they have ownership of the team.

We welcome payments via all major credit cards. Please note that any available store credit, whether from refund, credited activities, or converted from GiftCards, will be utilized as the primary payment method before attempting other payment options.

We provide a hassle-free 30-day full-refund policy for all premium workflows, no questions asked. However, please keep in mind that if you surpass a specific limit on returned workflows, you may face a temporary restriction on purchasing new workflows for a brief period.

Before making a purchase, we strongly recommend that you examine the workflows for available technical support options.  While premium workflows generally come with complimentary technical support from their authors, it's important to note that authors have the flexibility to:

  • Opt not to provide any technical support.
  • Offer paid support for premium workflows.
  • Provide paid support even when offering the workflows for free.

Additionally, maintainers of workflows can provide support for workflows independently of what the authors choose to offer. This is particularly common in the case of public workflows, where maintainers may offer paid support for publicly accessible workflows.

If you've acquired a workflow that includes free or paid services, you have the option to reach out to the author for technical support. The specific services authors can offer may vary, but they are typically closely related to the workflow you've purchased. These services can encompass:

  • Providing answers to queries regarding technical details, such as the usage of specific parameters and options, and their relevance to particular data types.
  • Assisting in the deployment of workflows for specific computational environments, which may include software application installations.
  • Customizing workflows to suit particular data types or alternative tools, tailoring them to your specific needs.

Authors typically specify the types of services they can offer in their service listings.

t's worth noting that the nature of services can vary significantly and depends on your negotiations with the seller. If you reach out to an author and request support based on their expertise, it may extend beyond the specifics listed in their service offerings.

To request a service, follow these steps:

  1. Identify a service listing from a workflow from which its maintainers offer services. It's important to note that the purchase of workflows and services are distinct processes, so you don't have to buy a workflow to request services.

  2. Request the service by specifying the type of service you require, the price you are willing to pay, and the timeframe in which you want it to be completed.

  3. Engage in negotiations on terms. The seller will respond and may seek further details, with the possibility of modifying the service terms based on your discussions.

  4. Make the payment for the service in advance. However, please be aware that the seller will not receive the payment until they have successfully delivered the service.

  5. Upon service completion, you can either accept or deny the delivery. If you are satisfied with the work provided by the seller, you can accept the delivery, thus concluding the request. If you are not satisfied, you have the option to deny the delivery and request revisions. In the event that no work is delivered or you no longer trust the seller's ability to deliver, you can submit a dispute and request the cancellation of the service request.

Bounties are excellent for increasing the visibility of your questions and showing appreciation to those who assist you. To post a bounty, follow these steps:

  1. Create or locate a question that interests you. It's important to note that you don't need to be the original poster of the question to post a bounty

  2. Click "Post a Bounty," specify the amount you wish to offer, and set the duration for the bounty.

  3. Click "Submit," and you will be prompted to pay for the bounty. If your account balance covers the cost, it will be deducted directly.

Once your question is posted with a bounty, anyone can answer it. You, as well as others, can evaluate the answers by upvoting or downvoting them. At the end of the bounty period, the bounty will be distributed among the answers based on the number of upvotes (minus downvotes) they have received. Here are some important details:

  • There is a minimum amount required to post a bounty.
  • The bounty duration can be set between 1 day and 2 months (60 days).
  • If there are no upvoted answers after 7 days, you can withdraw the bounty, and it will be returned to your balance as store credit, which can be used for future purchases or bounties. No refund will be issued.
  • Bounties without upvoted answers at the end of the bounty period will be canceled.

To prevent abusive use of bounties, only trusted users are allowed to upvote or downvote posts, and up or downvotes from answerers are disregarded.

Contributing Workflows

A workflow comprises two fundamental types of information: content and meta information. When contributing workflows to our repository, you must provide the following essential details:

Core content (unmodifiable after publication):

  1. Author: The individual responsible for creating the workflow. If you are not the author, it is typically recommended to contribute the workflow under the username "public," in which case you become the maintainer of the workflow.
  2. Title: A descriptive title for the workflow.
  3. Description: A comprehensive narrative detailing the workflow, including its background, input and output files, key data processing tools, runtime environments, and distinctive features.
  4. Main Document (optional): An optional main document relevant primarily to on-site workflows.
  5. Banner Image: At least one banner image with a designated "primary" image, serving as a thumbnail representation of the workflow. Our system can automatically retrieve images from main documents (for on-site workflows) and external websites (for external workflows), reducing the need to create banner images manually.
  6. Attachments (optional): Additional documents in various formats, encompassing source code, example input and output files, documentation, and other resources.
  7. View URL (optional): The URL enabling users to access the workflow, applicable only for external workflows.

A workflow will have a name, which is a succinct identifier automatically generated from the title but can be modified from the information panel before the workflow is published. The workflow will also be automatically assigned a version, which must be a numeric value. The URL to a workflow consists of the author's username, the workflow name, and its version.

These details constitute the "content" of a workflow, which becomes unmodifiable after the workflow undergoes publication following a review process.

Meta Information (Alterable by Authors and Maintainers):

  1. Version Tag: A more human-readable rendition of the workflow version, e.g., 0.1.0 or hg38.
  2. Maintainers: The individuals tasked with maintaining the workflow's content (if not yet published) or its meta information.
  3. Keywords: A catalog of keywords characterizing the workflow, facilitating connections with other workflows sharing similar topics, input-output files, operations, and tool usage. These keywords also aid in identifying users with expertise in related domains.
  4. Snippets: A compilation of code snippets extracted from the workflow's source, illustrating key workflow steps and data processing tool usage.
  5. Copyright: Indicates whether the workflow's copyright falls within the public domain or remains with its original author.
  6. License: Specifies how the workflow may be used and distributed.
  7. References: A compilation of references relevant to the workflow, including related publications or websites.
  8. Price: The cost associated with premium workflows, with the option to set different prices for volume or team purchases.

All of this meta information collectively assists in comprehending the workflows, their applications, and the establishment of connections between workflows and users possessing expertise in relevant domains.

BioWorkflows currently supports the following file formats as the main document for on-site workflows:

  1. Jupyter Notebook (*.ipynb): It is recommended to use Jupyter notebooks that contain both markdown and code cells. Our system will automatically generate an HTML preview of the notebooks from the notebook file. Folded cells are ignored, and any embedded images will be extracted to serve as banner images for the workflow. Please note that for premium workflows, the source code is masked so users who have not purchased the workflows will not be able to see the complete source codes.
  2. Rmarkdown (*.rmd): Rmarkdown files are supported and will be converted to HTML format for preview. However, due to the limitations of the format, there is no special handling for source code in this file format for premium workflows.

Workflows in alternative formats can be hosted on third-party services and registered as external workflows with BioWorkflows.


A workflow within our system can exist in one of the following modes:

  • Draft: The workflow is actively being developed and can be modified. They are not viewable by others unless they are explicitly shared, or are public workflows.
  • Pending: The workflow has been submitted for review and is awaiting evaluation.
  • Published: The workflow is officially published and accessible to anyone. While the core contents are fixed, modifications to metadata (e.g. tags) are still possible.
  • Archived: The workflow is archived and is not listed. It can be seen by its maintainers, and by users who have purchased the workflow. A draft workflow can be directly archived. No modification is allowed for archived workflows.

Published and achived workflows can be updated by forking the workflow and creating a new version.

For a visual representation of the workflow states and their transitions, please refer to the diagram below:

workflow modes

If you're aware of a workflow that could enhance our repository, you can assist in adding it in two ways:

  1. Propose the Workflow Anonymously:

    • Click on Workflows then select Suggest a Workflow.
    • Enter the URL of the workflow, submit, and let us handle the rest.

    The workflow will undergo screening and become available as a "Public Draft." Any user can volunteer to update it by requesting maintainer status for the workflow. The workflow will eventually be published.

  1. Upload the Workflow as a Registered User:

    • Log in to your account or create an account if you haven't already.
    • Click on Workflows then select Add a Workflow.
    • Adjust title, description, keywords, references etc, 
    • Submit the workflow for review, but select "publish as a public workflow during this process.

    The workflow will appear as a public workflow and you will remain a maintainer of it unless you choose to opt out of the maintainer status.


You have the option to enhance any workflow by

  • Suggesting the addition or removal of keywords. To do this, navigate to the workflow's information panel, click the    button, update the keyword list, and submit your changes. The modifications will be implemented after the workflow's author reviews and approves the suggestions.
  • Report problems and suggest revisions: If you notice something wrong with the workflow, you can report the issue by clicking the   dropdown menu and select Report. The report will be sent to workflow maintainers and our support team (or only our support team if you prefer).

If you wish to make more extensive alterations to the workflow, you can

  • Request to become a maintainer. To initiate this process, click the   button, provide a brief explanation of why you're interested in maintaining the workflow, and submit your request. You will assume the role of a maintainer once the workflow's author (or our site administrator, for public workflows) approves your request.
  • In the case of a public workflow that is still in draft status, you can also request to become the author. This is particularly useful if you authored a workflow that was contributed by others as a public workflow to our website. The process for claiming authorship of a workflow is similar to requesting to become a maintainer; just select "Request Ownership of Workflow" when requesting maintainer status. Once you become the author of the workflow, you will have full management privileges.

Becoming a maintainer of a workflow offers the added benefit of enabling you to create service listings and provide (paid) support for the workflow.

To add a workflow to the BioWorkflows Repository, follow these steps:

  1. Login or Create an Account: If you don't have an account, create one.

  2. Add the Workflow:

    • If you're registering an external workflow, go to "Workflows" and select Add Workflow. Enter the URL and click submit.
    • If it's an on-site workflow, click "Upload an On-Site Workflow."
  3. Modify Workflow Details: Adjust the name, keywords, descriptions, attachments. The system will flag any issues preventing you from publishing the workflow.

  4. Submit for Publication: Submit the workflow for review. If you want it to be published as a public workflow, select "publish as a public workflow" before submitting for approval.

  5. Approval Process: If your workflow doesn't contain sensitive information and doesn't have obvious copyright issues, it will be approved for publication.

Following these steps, you can contribute your workflow to the BioWorkflows Repository, optionally as a public workflow. The same process applies if you would like to upload a premium workflow, but you will need to first become a seller before you can set prices to your workflows.

If the source code of a workflow is available online (e.g. hosted on GitHub), it is easiest to use select snippet from attachments or external file to automatically extract code snippets from one or more source files. 

Here are some tips to help you import code snippets efficiently:

  • Identify Popular Workflow Languages: If the workflow is written in popular workflow languages like Nextflow, CWL, or Snakemake, our bot can automatically identify and extract code snippets from submodules. For example, in Snakemake workflows, you often only need to add the URL for the Snakefile.
  • Use Wildcard Characters: If the workflow consists of multiple files on GitHub, you can use wildcard characters to specify multiple files. For instance, you can add all R source files from a URL like this*.R 
  • Review and Adjust Tags: Code snippets are automatically tagged with keywords based on matching signatures. You may need to change the signature of tags if they tag the wrong code snippets.. 
  • Manual Review: The automatic snippet import process may include repetitive or uninteresting housekeeping steps. You can manually remove these snippets, although repetitive snippets (if sharing the same tags) and non-informative (non-tagged) snippets are not displayed by default.

By following these tips, you can efficiently import code snippets from online workflows, ensuring that the extracted snippets are relevant and well-tagged.


There are three ways to add new tags or edit existing tags:

  1. When you're editing a tag list, for example, when revising the keyword list of a workflow, you can create a new tag instead of selecting an existing one. Please note that these new tags won't have descriptions and won't be available for use by others. To edit these tags, go to Services -> Explore Expertise, then select My Keywords from the dropdown box
  2. Another way to add tag is to click the Propose a keyword button from the Explore Expertise page. You can enter the URL or name of a BioConda, Python package, etc., and select the type of keyword from the dropdown menu. Our system can automatically retrieve metadata for these tags. If your tag doesn't come from any of these known sources, you can enter the information directly by selecting "Enter Directly."
  3. To edit an existing tag, click  , then   Suggest Change,  make appropriate changes and submit for review. 

All new keywords and updates to existing keywords will be reviewed by our staff before being published as site-wide keywords. 


Code snippets are automatically tagged by keywords with matching signature, which matches content of the code snippets through regular expression.

The signature of keywords are specified by one or more fields in their metadata:

  1. library: This field specifies the name of a Python or R library, for example python:pandas or r:ggplot2. This signature will allow the tag to be matches to statements such as import pandas as pd and library(ggplot2).
  2. signature: This field is suitable for commands or function calls from bioinformatic tools or libraries. It can consist of either a string (name of the command or function, e.g. fastqc) or multiple values separated by "|"  (e.g.  fastaclean|fasta2esd  for a tool that can be identified from one or the two identifiers).
  3. regex_signature: This is the most generic form of regular expression that should follow POSIX regular expression for database query.  

To check or add signature of tags, go to the details page of a tag, click  , then   Suggest Change, add the corresponding fields to its metadata, and submit.

Tags with the same or similar meaning can often be retrieved from different sources or channels. For example, many Bioconductor packages are also distributed via Bioconda, and also registered at resulting in similar but not exact duplicate entries in our keyword database, such as  tool/biotools/APAlyzer, tool/bioconductor/APAlyzer, and tool/bioconda/bioconductor-apalyzer.

To avoid duplicated tagging while still keeping tags from different channels, some tags are assigned the metadata "alias_of=name_of_primary_tag," which designates them as aliases to corresponding primary tags. Only primary tags are used to tag workflows, topics, and code snippets, although the aliases can still be used to enter them.

You can follow the procesure of adding or editing a tag to set the alias_of metadata for an existing tag. This helps maintain a clean and efficient tagging system while allowing users to find relevant content regardless of the source or channel.


Selling at BioWorkflows

We appreciate your interest in becoming a seller on To guide you through the process, here are the steps you'll need to follow:

  1. Eligibility Check:

    • Before proceeding, it's essential to determine if you meet the eligibility criteria to become a seller.
    • If your involvement on the platform primarily involves answering occasional questions or distributing free workflows, eligibility concerns are typically minimal.
    • However, if you intend to offer a substantial number of high-quality workflows and services, you should ensure that you qualify as a freelancer and understand its tax implications and conflict of interest with your other duties.
    • Be aware that your current employment situation may affect your eligibility, especially if your work involves copyrighted material.
  2. Account Registration and Seller Status:

    • Begin by registering an account on
    • Access your account settings and navigate to the "Become a Seller" option.
    • During this process, you will be required to agree to our terms of service and acknowledge essential notices, including those related to the copyright of workflows.
    • In some cases, we may request additional verification from you.
    • Set up one or more payout methods to facilitate payment receipt.
    • We highly recommend creating "expertises" and ensuring that your profile is publicly accessible. This allows other users to discover your offerings based on your expertise.
  3. Service Offerings:

    There are various methods through which you can provide your services as a seller:

    • Creating and Selling Workflows: You can develop workflows and set a price for each copy sold.
    • Offering Paid Services: Consider providing paid services associated with selected workflows.
    • Active Participation in the Discussion Forum: Engage with the community by answering questions in our discussion forum. You can earn bounties by responding directly to questions or by referring users to your own workflows.

By following these steps, you can effectively become a seller on and showcase your skills and offerings to the platform's users. We look forward to your contributions and expertise on our platform.

The process of uploading a premium workflow is the same as uploading a regular workflow. However, you will need to become a seller before you can set the price of workflows and list them as premium workflows.

The content of workflows cannot be altered once they are published. You can however always fork a workflow to create a newer version.

  • After you publish a forked workflow, the newer version will become the default version.
  • The old version are still available from the workflow details page. In this way you can create a variations of the same workflow (e.g. one for mouse and one for human) and you even set the name of the variants to make them easier to remember.

If you have set up GitHub integration to the workflow, pushing to a published workflow will automatically create a new version of the workflow in draft mode.

You can update the content of an external workflow without needing to update its metadata on its corresponding entry on If you host your workflow in a GitHub repository (which can be private, as is the case with premium workflows), you can update the content of the workflow through an automated process. To achieve this, you will need to:

  • Integrate your account with GitHub. You can either sign in with your GitHub account, or link your GitHub account with your BioWorkflows account after signing in.
  • Create and maintain your workflows in GitHub repositories
  • When you upload your workflows to BioWorkflows, add the blob URL to "Auto-update from GitHub"

After the workflow is uploaded, pushing changes to your GitHub repositories will automatically update the workflows on More specifically,

  • If your workflow is in draft mode, the content of the workflow will be replaced by the new version.
  • If your workflow is already published, a new draft version will be created.

At BioWorkflows, showcasing your expertise in specific areas is a prerequisite before creating service listings related to a workflow. To initiate service provision, follow these steps:

  1. Obtain seller satus.
    • Start by registering and creating an account.
    • Submit a request to become a seller, bearing in mind that seller status entails specific restrictions and responsibilities.
  2. Publish a workflow
    • Publish a workflow in your areas of expertise, ensuring it includes clear background information, input details, operations, sample outputs, and a description of the running environment for which the workflow should be deployed.
    • Alternatively, request to become a maintainer for a public workflow or one from your team members. Revise workflows as needed, because many public workflows lack detailed descriptions.
  3. Create a service listing
    • Detail your service by creating a listing, specifying the service particulars, expected rates, and delivery timeframes.
  4. Accept and provide services
    • Stay vigilant with your email communications and promptly respond to user requests.
    • Engage in negotiations regarding service details and set realistic completion expectations.
    • Diligently work on the service request, making every effort to meet the agreed-upon timeframe.

By following these steps, you not only fulfill the prerequisites for creating service listings on BioWorkflows but also acknowledge the responsibilities that come with seller status. This ensures a transparent and well-informed engagement for all involved parties on the platform. If you have any inquiries or need support, feel free to reach out—we're here to assist you.

To access your available funds, you need to configure a withdrawal method via your seller settings page. It's important to be aware of our withdrawal policy, which includes the following key points:

  1. Pending Sales Period:

    There's a grace period during which sales are considered as pending. During this time, users have the option to return your workflows without any questions asked.

  2. Finalized Sales:

    After a period of 30 days, all sales become final. This means that you can only withdraw funds from workflows that were sold more than 30 days ago.

Linking to BioWorkflows

Badges are compact tiles containing links to various pages on They serve as quick access points to workflows featured on the website. There are three types of badges you can use:

  • workflow icon :  The generic "bioworkflows" badge, which links to a specific workflow.
  • The "listed on bioworkflows" badge, indicating that the workflow is showcased on our website.
  •  The "supported at bioworkflows" badge, signifying that the paid (or free) support is available through bioworkflows.

To incorporate any of these badges into your workflow, follow these steps:

  1. Visit the information panel on the workflow details page.
  2. Choose either the Markdown or HTML version.
  3. Copy the provided code snippet.
  4. Insert the snippet onto the homepage of your workflow.

The code snippet page associated with a keyword offers practical examples of how the tools can be utilized, effectively functioning as an alternative form of documentation for the tool itself. We provide a badge tag icon that includes a link that compiles all the code snippets related to a specific keyword, making it a valuable resource for users.

To embed this badge on your software tool's homepage, follow these steps:

  1. Locate a tag that is relevant to your tool from either the workflow list or the details page.
  2. Click the tag, look for the "</>" icon; click it to access the code snippet page associated with the tag.
  3. Scroll to the end of the snippet listing page and select the "Add a badge to your website" link.
  4. Depending on your website's development framework, choose either the HTML or Markdown version of the badge for seamless integration.
  5. Copy the source code for the badge and insert it into the appropriate locations on your website's homepage.

Can't find what you are looking for?

Write to us and let ue know!