Translate the file and table in Notion

Language Our tech team speaks English, Russian and German. You can choose any of these languages for your text deliverable and the review call. ObjectiveWe operate production-ready AI and document workflows on n8n Cloud that integrate Salesforce with LLMs and document services. While the workflow logic itself is functional, our deployment pipeline is broken. Moving a workflow from DEV to TEST to PROD—and connecting n8n to our changing Salesforce sandboxes—currently requires manual intervention and has been completely blocked for several weeks.We are engaging an experienced integration architect to review our current setup. The primary focus is to establish a reliable, automated deployment process for our existing features. Simultaneously, because we have experienced significant downsides with n8n, this review must deliver a clear strengths vs. weaknesses analysis of n8n to help us decide whether to commit to it or adopt a new tech stack for future features.This is a scoped evaluation engagement.No implementation work is included.Scope of DeliverablesA written assessment of two to four pages, followed by one review call. The assessment must address three core questions: Retain vs. Replace (with Strengths & Weaknesses Analysis):Provide a clear-eyed evaluation of n8n’s capabilities and limitations regarding our environment topology. We need to decide if we stick with n8n or transition future features to an alternative stack (e.g., self-hosted n8n, a higher n8n tier, or a different orchestration/code-first platform). Include a definitive strategic recommendation and its technical rationale. Licensing & Platform Constraints:Investigate and map the precise platform limitations and licensing boundaries of our current tier versus alternative tiers or self-hosted variations. The review must address: Feature & License Alignment:Analyze whether our current deployment blockages are caused by absolute platform restrictions, process-based misconfigurations, or native tooling limitations. Do not assume a higher license tier is the default or necessary solution. Native Environments & Git Functionality:Provide an objective assessment of n8n's native source control and environment promotion features (including explicit availability, gating criteria, and limitations when coordinating multiple projects/workspaces). Cost-Benefit and Feature Mapping:If specific deployment or environment automation features require an upgrade, identify the precise feature names, technical constraints, and current pricing structure. Weigh this clearly against the operational cost and overhead of moving to a self-hosted architecture. The Critical Path: For existing features:Define the immediate, actionable steps required to make our current deployment process automated and reliable. For future features:If a replacement stack is recommended, define the high-level target architecture.Out of Scope:Detailed migration project plans, granular effort estimation, and hands-on code changes. We require expert technical judgment, not a project management plan.Company and System ContextOur core system is Salesforce, customized with a managed recruitment package. n8n acts as our middleware, handling the heavy lifting for AI processing and integration logic triggered by Salesforce.Currently, we run three environments within a single n8n Cloud workspace split into three projects: Environment n8n Project Salesforce Target DEV DEV Developer Sandbox TEST TEST UAT Sandbox PROD PROD Production Workflow ArchitectureOur pipeline includes a three main LLM supported tools, and shared sub-workflows handling Salesforce authentication and HMAC verification.Workflows share identical names across all three projects. Environment-specific values (Client IDs, secrets) are isolated as project variables so that the core workflow logic remains uniform. Salesforce requests to n8n are secured via HMAC headers, and n8n authenticates back to Salesforce via OAuth. The system is designed to be dynamic: Salesforce passes its own instance URL in the webhook payload, meaning n8n should not need hardcoded sandbox URLs.Current Deployment Process & Known IssuesPromotion between environments is handled project-to-project via an in-house Bash script that transfers the workflow JSON and attempts to remap credential IDs to the target project. A Git repository is used for version control and code review, but it is entirely decoupled from the deployment pipeline; synchronization between Git and n8n is entirely manual.This custom scripting was built because native environment promotion features appear locked behind higher enterprise license tiers.Critical Bottlenecks: Deployment Blockage:End-to-end promotion from DEV to PROD is completely stalled and has been for several weeks. Opaque Root Cause:It is currently ambiguous whether our blockers stem from platform license limits, tooling deficiencies, or internal process gaps. Environment Serialization:Connecting n8n to a new Salesforce sandbox demands manual reconfiguration, creating a severe bottleneck that serializes developer workflows. Manual Friction:Multiple post-promotion steps still require manual intervention, and we lack clarity on which steps are hard platform constraints versus addressable automation gaps.Required Expertise Deep production experience with n8n in both Cloud and self-hosted environments, including precise knowledge of license tier gating. Extensive experience integrating n8n with Salesforce via OAuth, specifically managing sandbox-to-production lifecycles and webhook security (HMAC). A pragmatic approach to architecture, with a willingness to recommend deprecating custom-built in-house scripting in favor of robust automation. Exceptional technical communication skills, with the ability to translate complex architectural trade-offs into clear English for a non-engineering Product Owner.Provided Upon EngagementRead access to the n8n workspace, a Salesforce testing sandbox, our internal process documentation, and the Git repository. A dedicated technical contact for both Salesforce and n8n sides will be available. Note: Credentials and production secrets are strictly excluded from this public posting.Proposal RequirementsTo be considered, your proposal must explicitly address the following three points: