Master ProcessArchitec

Kickoff Checklist

1. Prepare your intake data. Capture the business snapshot, pain points, and manual time estimates. Those answers power the AI analysis.
2. Launch the generator. Click Launch Generator from the hero banner. Toggle Expert Mode if you already have a detailed workflow description, then submit.
3. Review the output. The Output Viewer presents a narrative summary, node-by-node details, and a downloadable JSON that is ready for import.
4. Download the Quick Start PDF. Get the ProcessArchitec Quick Start Guide for a handy reference.

Core Endpoints

Authentication

All routes expect a Supabase JWT. Client-side requests attach the token from supabase.auth.getSession(). Server-to-server tasks can use SUPABASE_SERVICE_ROLE_KEY but never expose it to the browser.

Example Request & Response

Request:

POST /api/workflow/generate
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
Content-Type: application/json

{
  "userInput": {
    "businessSnapshot": {
      "industry": "ecommerce",
      "companySize": "50-200",
      "currentTools": ["Shopify", "Stripe", "Slack"]
    },
    "workflowDescription": "When a Stripe payment succeeds, create a customer record in HubSpot and notify the sales team in Slack"
  },
  "outputFormat": "n8n"
}

Success Response (200):

{
  "success": true,
  "workflow": {
    "name": "Stripe Payment to HubSpot & Slack",
    "nodes": [...],
    "connections": {...}
  },
  "meta": {
    "outputFormat": "n8n",
    "nodeCount": 7,
    "processingTime": "12.3s"
  }
}

Error Response (401 Unauthorized):

{
  "error": "Authentication required",
  "message": "Please sign in to generate workflows"
}

Error Response (422 Validation Error):

{
  "error": "Validation failed",
  "message": "workflowDescription is required",
  "details": {
    "field": "userInput.workflowDescription",
    "issue": "missing_required_field"
  }
}

n8n Import & Testing

1. Open Workflows → Import from File in n8n and upload the JSON from ProcessArchitec.
2. Add your credentials to OAuth nodes (Google, Slack, etc.). Your workflow arrives 80-95% configured—you only add the keys.
3. Use n8n's built-in Test Workflow feature to execute nodes individually or test the entire flow.
4. For webhook triggers, copy the production webhook URL and use tools like Postman or curl to send test payloads.
5. Review execution logs in n8n's interface to debug data flow between nodes.

Make.com Import & Testing

1. Upload the generated JSON through the Make.com scenario editor (Create Scenario → Import Blueprint).
2. Re-map modules that require OAuth credentials and configure API keys for your services.
3. Use Make's Run Once feature to test your scenario with real or sample data.
4. Configure error handlers for retries, notifications, or fallback logic for production reliability.
5. Review execution history to verify data transformations and module outputs.

Security & Credential Best Practices

• Never commit credentials to version control. Use environment variables or secure vaults (1Password, AWS Secrets Manager).
• Rotate API keys quarterly and immediately if a key is exposed or an employee with access leaves.
• Use separate credentials for development, staging, and production environments.
• Enable OAuth2 where possible for automatic token refresh and better security than static API keys.

Prompt Design for Better Workflows

The quality of your generated workflow depends on the clarity of your input. Follow these guidelines for best results:

• Define the trigger clearly: "When a paid Stripe invoice arrives" vs. "when payment happens"
• Specify data sources and destinations: "Pull customer data from HubSpot, create deal, store in Google Sheets"
• Include transformation logic: "Calculate order total by summing line items and adding tax"
• Define success criteria: "Send Slack notification to #finance when complete, email customer if payment fails"
• Mention edge cases: "If inventory is zero, notify warehouse team and pause order"

Example: "When a new Typeform submission arrives, validate the email address, check if the contact exists in HubSpot (create if not), add them to the Q1 Campaign list, send a Slack notification to #sales with contact details, and schedule a follow-up task in Asana for 3 days later."

Testing & Deployment Strategy

• Review before importing: Check the generated workflow in the Output Viewer to verify logic matches your requirements.
• Test in n8n/Make first: Use platform-native test modes to validate each node with real or sample data.
• Start with staging: Deploy to a test environment with non-production credentials before going live.
• Monitor after deployment: Check execution logs daily for the first week to catch edge cases.
• Version control your workflows: Export and commit workflow JSON to Git for change tracking and rollback capability.

Security & Compliance

• Enable row-level security (RLS) on Supabase tables to ensure users only see their own workflows.
• Never hardcode credentials in workflows—use platform credential managers (n8n credentials, Make connections).
• For sensitive data, implement field-level encryption and comply with GDPR/CCPA data retention policies.
• Monitor usage through your dashboard and set up alerts before hitting API rate limits on connected services.

Comprehensive Platform Coverage

Three-Layer Parameter Generation System

Our proprietary configuration system ensures workflows arrive 80-95% complete:

Intelligent Architecture Guarantees

Our Hybrid Architecture System ensures comprehensive workflow coverage:

• •Optimized node distribution: Workflows are designed with the right number of nodes for your use case—whether 3 or 30—ensuring no single node or module is overwhelmed with too many tasks
• •Service coverage analysis: System detects missing services and supplements architecture to ensure complete automation
• •Native node preference: Workflows rely primarily on native nodes and modules with limited HTTP Request fallbacks for optimal reliability and maintainability
• •Quality preservation: All generated nodes maintain 80-90% parameter completion standard regardless of workflow complexity

What This Means for You