🔗 Routing via GitHub

GitHub routing

If your team already works with Git, why manage call routing differently? GitHub routing lets you store your routing configuration in your own repository. Push a commit, and CallFactory automatically fetches the file, validates it, and applies the changes to your live call flow.

This gives you everything Git offers: version history, diffs, pull requests, code review, branching, and instant rollback. Your call routing becomes part of your codebase — managed with the same tools and workflows your team already uses.

Auto-sync routing from your GitHub repo
Full version history and instant rollback
Works with CSV, TXT, and JSON files
Built for DevOps teams and CI/CD pipelines

Benefits of GitHub routing

Discover how our features help you work smarter, save time, and improve how your business communicates.

📥

Fully automated updates

Push a commit to your repo and the routing changes are applied automatically. No manual upload, no support ticket, no dashboard interaction.

🔐

Version history and rollback

Every change is tracked in Git. If something goes wrong, revert to the previous commit and your routing is restored in seconds.

👨‍💻

Built for developers

Use the same workflows your team already knows — branches, pull requests, code review — to manage call routing alongside the rest of your infrastructure.

How GitHub routing works

You connect your GitHub repository to CallFactory using a Personal Access Token (PAT). Point us to the file that contains your routing rules — a CSV, TXT, or JSON file in your repo. From that moment on, every push to the main branch triggers an automatic sync.

CallFactory fetches the file, validates every entry, and applies the changes to your live routing. If the file contains errors, the sync is rejected and you receive feedback on exactly which lines need fixing. Your current routing stays untouched until a valid file is pushed.

Version control for call routing

The biggest advantage of GitHub routing over file-based routing is the version history. Every change is a Git commit with a timestamp, author, and message. You can see exactly who changed what, when, and why.

If a routing change causes problems, you do not need to rebuild the previous configuration from memory. You revert the commit and CallFactory automatically restores the previous routing. This is especially valuable for complex setups with hundreds of rules — where a manual rollback would take hours, a Git revert takes seconds.

Integrate with CI/CD pipelines

Because the sync is triggered by a Git push, it fits naturally into CI/CD workflows. Your deployment pipeline can generate a routing file as part of the build process, commit it to the repo, and the routing update happens alongside your code deployment.

For example, if your application has a staging and production environment with different call flows, you can manage both from separate branches. Merge to staging to test new routing, then merge to main to push it live. The same review and approval process you use for code applies to your call routing.

Works with all routing features

GitHub routing supports the same file formats and routing rules as file-based routing. Update PIN codes, allowlists, denylists, area code rules, zip code rules, or entire IVR flows — all from your repo.

Your routing files stay in your own private repository. CallFactory only reads the specific file you have pointed us to. You retain full control over your data, access, and repository settings.

Included free with every number

GitHub routing is included at no extra cost with every CallFactory number.

This feature is included free with every business number or International number.

File-based routing

Upload a CSV, TXT, or JSON file to update call routing in bulk. Change hundreds of rules at once — PIN codes, allowlists, denylists, area codes, or entire IVR flows.

API integrations

Tell us what you need, we build the endpoints. Our private API lets you integrate CallFactory telephony into your own software — no generic library, no guesswork, no wasted development time.

Webhook call routing

Route calls dynamically using your own webhook. When a call comes in, CallFactory asks your server where to send it — full control in real time.

Provide a Personal Access Token (PAT) and tell us which repository and file to watch. CallFactory connects and starts syncing automatically.

CSV, TXT, and JSON — the same formats used by file-based routing.

Every push to the main branch triggers CallFactory to fetch the file, validate it, and apply the changes. You can also configure a different branch if needed.

Yes. The PAT handles authentication securely. CallFactory only reads the specific file you have pointed us to — nothing else in your repo is accessed.

The sync is rejected and you receive feedback on which lines have problems. Your current routing stays untouched until a valid file is pushed.

Revert the commit in Git and push. CallFactory fetches the previous version of the file and restores your routing automatically.

PIN codes, allowlists, denylists, area code rules, zip code rules, and entire IVR flows — the same as file-based routing.

No. It is included free with every CallFactory number.