Workflood is a dedicated programmable automation platform for HubSpot teams. It enables developers and revenue operations teams to run custom-coded workflow actions in TypeScript or Python, deploy 20+ turnkey templates, and connect external APIs with flat monthly pricing.

How is Workflood different from HubSpot Data Hub (Operations Hub)?

Workflood is an independent, code-first automation runtime that runs alongside HubSpot. It offers flat monthly pricing at $79/mo for Single Portal without per-seat fees or credit metering, supports dual TypeScript and Python 3.11 runtimes in isolated gVisor containers, and connects to any third-party API.

What programming languages are supported for custom workflow actions?

Workflood natively supports TypeScript (Node 20) and Python 3.11 with full HubSpot SDK injection, Monaco editor autocomplete, instant dry-runs, and version history with instant rollback.

How does Workflood pricing work?

Workflood uses flat workspace pricing with no per-seat fees or usage credits. Single Portal is $79/mo with unlimited team seats, 50,000 runs per month, and 1 production HubSpot portal (+ sandbox). Multi-Portal / Agency plans provide unlimited client portals and custom high-volume runs.

How is user code securely executed in Workflood?

User code runs in dedicated gVisor container sandboxes with memory limits, strict execution timeouts, read-only root filesystems, and encrypted secrets storage using libsodium XChaCha20-Poly1305.

Workflood

DevOps & CI/CD

5 min readUpdated August 2026

How to Set Up Two-Way GitHub Sync for HubSpot Actions

Connect your GitHub repositories to version control HubSpot custom actions, enable pull request code reviews, and automate deployments.

Table of Contents

• Why Git Version Control Matters for RevOps
• Connecting a GitHub Repository
• Repository Directory Structure
• Branching & Deployment Workflows

Why Git Version Control Matters for RevOps

In native HubSpot, custom code is edited directly in a browser text area without pull request reviews, branch protection, or Git history. A single accidental edit can break critical revenue workflows.

**Workflood Two-Way GitHub Sync provides:** - **Code as Source of Truth:** Push action code from your local IDE (VS Code, Cursor) or let edits in Workflood commit back to GitHub. - **Pull Request Code Reviews:** Review operational code changes before deploying to production HubSpot portals. - **Instant Rollbacks:** Revert to previous Git tags or commits with one click.

Connecting a GitHub Repository

In Workflood, navigate to **Settings > Integrations > GitHub**.
Click **Connect GitHub** and authorize the Workflood GitHub App on your organization or repository.
Select your target repository (e.g., `your-org/hubspot-workflows`) and target branch (e.g., `main`).
Select your synchronization directory (default: `/actions`).

Repository Directory Structure

Workflood structures action files neatly inside your repository with matching configuration manifests:

repository-tree.txt

hubspot-workflows/
├── actions/
│   ├── lead-routing/
│   │   ├── handler.ts
│   │   └── config.json
│   ├── contract-renewal/
│   │   ├── handler.py
│   │   └── config.json
│   └── company-dedupe/
│       ├── handler.ts
│       └── config.json
└── README.md

Branching & Deployment Workflows

When a developer opens a pull request in your GitHub repository: - Workflood runs automated syntax and TypeScript type checks. - Once merged to `main`, Workflood automatically compiles and activates the new version in your production workspace.

Frequently Asked Questions

Can I edit code directly in the Workflood UI if GitHub sync is enabled?

Yes. When you save changes in the Workflood Monaco editor, Workflood automatically commits the change to your connected branch with a descriptive commit message.

Previous Guide

Managing Secrets & API Keys Securely with Libsodium Encryption

Next Guide

Overcoming HubSpot 20-Second Workflow Execution Timeouts