Integrater

Inspiration

I have owned the 'integrater.co' domain for more than a decade and have started building this project several times over the years.

The idea has always been straightforward: make it easy for people to connect the applications they already use and automate work between them. The difficult part was never the workflow interface itself - it was creating integrations.

Previously, every new application connection required someone to study the provider's API documentation, understand authentication and webhook requirements, implement triggers and actions, test edge cases, and maintain the integration as the API evolved. A single connection could take up to a person-week to build.

By the time a small set of integrations was completed, previously built connections could already require updates or become deprecated. Fixing those connections delayed new ones, and without a large dedicated integration team, the project could never reach the breadth of integrations needed to become useful.

Codex changed what is possible. Its ability to browse API documentation and write code makes it possible to research and build integrations in parallel rather than one at a time.

What it does

Integrater is a workflow automation platform where end users can connect multiple applications and automate actions between them.

Users can create workflows with:

• A trigger, initiated by:
  • An incoming webhook, or
  • An event inside a connected application
• One or more action steps
• Actions spanning multiple applications in a single workflow

For example, a workflow can start when an event occurs in one app, then create a spreadsheet row, send an email, publish content, or perform other actions in connected services.

The current project includes connections and workflow mappings for services such as:

• Facebook Pages
• Gmail
• Google Sheets
• Webhooks
• YouTube

How we built it

Integrater uses a React frontend built with MUI and Creative Tim's Soft UI Dashboard PRO React template.

The project-specific frontend includes:

• A workflow builder for configuring triggers and multi-step actions
• A dashboard for managing workflows
• Route definitions for the Integrater application

The backend is written in PHP. Each app integration is organized as a connection directory containing:

• connection.php - the backend implementation for the connection
• connection.json - the frontend mapping for the integration's triggers and actions

To make integration development repeatable, we created a connection.md skill and process. It guides Codex through researching an application's API documentation and producing the corresponding PHP backend implementation and JSON frontend mapping.

All included project-specific code was coded by Codex, using either GPT-5.6-Sol or GPT-5.6-Terra.

GPT-5.6-Sol was used to generate backend, connections template and to develop the reusable connection-building skill, while GPT-5.6-Terra uses that skill in Codex across multiple conversations to build multiple integrations in parallel.

Challenges we ran into

The main challenge is the same one that stopped previous attempts at building Integrater: integrations are expensive to create and maintain.

Every external platform has its own:

• Authentication approach
• API conventions
• Webhook implementation
• Trigger capabilities
• Action requirements
• Versioning and deprecation schedule

Historically, learning and implementing each API connection could take up to a person-week. A small team could spend all of its time catching up with changing APIs instead of expanding the product.

What's next for Integrater

Next, we plan to expand the number of supported applications and continue improving the connection-building process.

Our priorities include:

• Building dozens of additional application connections
• Adding more triggers and actions for existing integrations

The long-term goal is to make Integrater a practical automation platform with a broad and rapidly growing set of app connections.

Built With

• mysql
• php
• react