Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Web resources

    Organization, collaboration and automation

    Workflow tools should first make decisions, owners, dates and versions visible. Simplify a process before automating it, and plan what happens when an automation fails.

    Take a real content approval: author, reviewer, decision, published version and correction. Test who receives a notice and how to find the decision three months later.

    AI-generated illustration

    Editorial method

    A directory made to be useful, not merely long.

    Selection prioritises recognition within the field, professional use and reference status. Highly specialised documentation entries are consolidated under their main resource.

    01

    Official foundations

    Standards bodies, official documentation and public authorities are used as primary reference points.

    02

    Professional tools

    Established services are grouped by actual use: building, hosting, measuring, securing, publishing or promoting a website.

    03

    Independent reading

    Inclusion is editorial and unpaid. A listing does not imply a partnership or guarantee.

    Before choosing

    Compare on three practical questions

    Organization, collaboration and automation
    CriterionQuestion to resolve
    OwnersDo tasks, decisions and approvals have identifiable owners?
    Failure casesHow are duplicates, synchronisation errors and stopped workflows detected?
    DocumentationCan another person find decisions and resume the process?

    Keep a short decision record: requirement, source, observed result and unresolved point. Test the same task with each candidate instead of comparing marketing lists of features.

    Search and filter

    Official starting points for this topic

    Compare their role and documentation before selecting a tool. Inclusion is not a ranking.

    13 resources displayed

    The date applies to the linked document, not to a review of every service feature.

    Organization, collaboration and automation

    n8n

    Workflow automation tool connecting applications and APIs, available in cloud or self-hosted deployments. Review its fair-code license and terms for the intended use.

    n8n — Documentation · Source consulted

    Use it for : Test a fictional event through to its result, then replay a duplicate and a destination-service failure. Assign execution monitoring and error recovery; self-hosted deployments also need updates, backups and access protection.

    Documented characteristics
    Installation
    Docker · Docker Compose · npm
    Editions
    Community · Business · Enterprise
    Hosting
    Self-hosting

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    Fictional example: a form sends an event to n8n and receives a positive response, but no customer record appears. The acknowledgement does not establish that the write succeeded.
    Useful check
    Check the URL, workflow publication and matching run in Executions. Then compare the write node’s result with the state actually stored in the destination service.
    Interpretation and next step
    If the response was immediate, treat it as evidence of startup. Do not replay blindly: use the event identifier and deduplication rules before any recovery.

    Official documentation ·

    Official documentation · n8n — Webhook node

    EuropeTool / software
    n8n.ioVisit official website
    Organization, collaboration and automation

    GitHub Actions

    Automation of tests, checks and deployments from GitHub repository events. Define trigger event, jobs and execution environment in the workflow. Inspect permissions and logs; one successful job does not prove that every expected check ran.

    GitHub Actions · Source consulted

    Use it for : Define test and release steps while limiting automation permissions.

    Documented characteristics
    Format
    YAML
    Configuration
    .github/workflows/*.yml
    Triggers
    push · pull_request · workflow_dispatch
    Metrics
    status · conclusion
    Resources
    id · head_sha · run_attempt

    Learning example: adapt files, identifiers and conditions to a test copy before interpreting the result.

    Practical example
    To read a GitHub Actions result, compare two fictional responses: status: completed with conclusion: failure, then status: queued with conclusion: null. The first run has finished unsuccessfully; the second is still waiting to start. A completed status alone therefore does not prove that checks passed.
    Useful check
    Associate the result with its id, the expected head_sha commit and the run_attempt number. An older successful run on the same branch does not automatically validate the latest code. When a run is attempted again, keep the connection between the commit and the result being reviewed.
    Interpretation and next step
    A success conclusion describes the checks actually executed by the workflow. Review the intended jobs and their logs before concluding that the site works for visitors. Keep the identifiers needed for traceability without copying a token or secret into an acceptance record.

    Official documentation ·

    Official documentation · GitHub REST API — Workflow runs

    InternationalService / platform
    github.comVisit official website
    Choose a starting point

    What each category helps you decide.

    These examples illustrate uses, not rankings or endorsements. Verify each provider’s current documentation and terms before a decision.

    Organization, collaboration and automation

    Workflow tools should first make decisions, owners, dates and versions visible. Simplify a process before automating it, and plan what happens when an automation fails.

    Questions to check
    • Define the source of truth for documents and approvals.
    • Test access roles, exports and useful notifications.
    • Test handover, a collaborator leaving and recovery of work before adoption.

    A practical use : Take a real content approval: author, reviewer, decision, published version and correction. Test who receives a notice and how to find the decision three months later.

    What this cannot prove : Automating an unclear step can spread an error faster. Check access roles and data export before moving the team.

    Examples : Notion · Trello

    Related guide : Take over or hand over a website with confidence

    Explore troubleshooting situations

    Troubleshooting methods

    A workflow tool becomes useful when work status, version and ownership remain understandable. These cases examine recovery after failure, approval and document recovery. They can be tested with a small process copy and demonstration data.

    Restarting an automation creates two tasks

    What you observe
    After a delay or response error, the same event is retried and triggers several tasks, notifications or records.
    Before drawing a conclusion
    Recovery may process an already accepted operation again. Visible status needs to distinguish a new event from a repetition.
    Verification step
    In a demonstration flow, cause an interruption then replay the same event. Inspect identifiers and outcomes. Define expected handling of repeats before enabling the flow for real messages or actions.

    An approved document changes without a fresh review

    What you observe
    The version used for publication no longer matches the version its owner reviewed and approved.
    Before drawing a conclusion
    An “approved” status attached only to a document can become ambiguous when its content changes. The decision must connect to the relevant version.
    Verification step
    Check the approval date, content and owner. Define how a change reopens review and how the published version can be found. Do not infer current permission from an old comment.

    An export retains titles but loses attachments

    What you observe
    The exported table retains tasks and status, while documents, useful discussions or relationships cannot be recovered from the file.
    Before drawing a conclusion
    Exporting a list does not establish recovery of the entire process. External files and links need separate checks.
    Verification step
    Choose a complete task with attachments and decisions. Rebuild it from the export in a copy, then list missing elements and required recovery formats before approving the exit process.
    Another case to examineThe document changes owner, but its automation does not
    Situation
    A folder moves to a new team while reminders still depend on the previous owner’s account. Transferring content does not transfer every dependency.
    Before drawing a conclusion
    Replacing a name in a document does not make the process independent and maintainable.
    Practical check
    List the owner, trigger and service account for each step. Run a trial without the former account and check notifications, permissions and recovery procedures before closing the handover.

    Keep useful data when changing tools

    Before making a resource part of website operations, plan for updates and an exit too. These checks concern your trial results without assuming features or prices of a particular plan.

    Export relationships

    Check tasks, owners, useful comments and links between objects. A title list can lose dependencies required for follow-up.

    Identify automation

    Inventory triggers, conditions, messages and connected systems. A forgotten rule can keep sending notifications after migration.

    Test continuation

    Repeat a small process with failures and final decision. Check who owns the data and where the team finds the current state.

    Transparency

    Editorial scope and third-party websites

    This non-exhaustive directory had its data consistency and links checked on 2 October 2026. Some websites restrict automated checks. It contains external links to independent websites. Their availability, content, prices, cookies and terms may change. Française du Numérique does not control them and receives no commission for their inclusion.

    Directory questions

    Selection, independence and updates.

    Entries describe resources from their publishers’ pages and provide a source, category, purpose and checking date. The selection covers different Web tasks rather than ranking every available provider. Open the cited source to check current scope, availability and conditions before relying on a service.

    No. Inclusion identifies a resource to examine; it does not certify every feature, price, policy or result. Compare the resource with your actual task, country, language and technical requirements. Confirm current conditions with its publisher before committing time, data or money.

    Yes. Search the displayed catalogue, combine the available filters and clear them to return to the full list. Every entered word must match the indexed text. The visible result count describes this selection, not the entire Web. Individual category pages and direct links remain available without JavaScript.

    Choose a repetitive task whose input, outcome and owner are already clear. Check missing-data cases, failures and recovery before expanding it. Automation does not resolve undefined approval or responsibility.

    Specify the reference location, owner and approval rules. Connect shared copies to that source and identify their date or version. Test what another person finds through usual links, particularly after a change or handover.

    Compare using observable evidence

    Before choosing a resource, run a limited trial using the same data and task. Keep the outcome and its limitations rather than a ranking based on familiarity.

    Test a complete task with attachment, approval and export. Replay an event in a copy to detect duplicates. Compare approved version, owner and recoverable data; exporting a list does not establish recovery of the full process.

    Use precise terms

    Two distinctions before comparing resources

    Automating a step requires distinguishing execution, checks and validation.

    Documented reference points for this topic

    Documented reference points for this topic
    ReferenceValue or syntaxScope
    GitHub REST API
    60 / h · 5 000 / hGeneral limits: 60/hour per unauthenticated IP; 5,000/hour per authenticated user. Exceptions and secondary limits apply.
    RFC 4180 · CSV
    text/csv · "a,b"Fields containing commas, quotes or line breaks are quoted; internal quotes are doubled.
    RFC 3339 · Date-time
    2026-10-22T09:00:00+02:00The explicit offset relates local time to UTC; this example is not an appointment.
    GitHub Docs · Repository backup
    git clone --mirrorA mirror clone backs up the Git repository and its history. Git LFS objects require an additional fetch, and a wiki has its own repository. For a handover, also inventory data and services that do not reside in Git.

    Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.