Integrations

Webhooks first, honestly.

Q: Can Chromoly replace my Zapier or Make setup?

Often, yes - because most automation stacks exist to move data between tools and a spreadsheet. Chromoly generates the system of record and runs the automation inside it, so the wiring problem shrinks. See the honest comparisons vs Zapier and vs Make for where each wins.

Chromoly doesn't have a 5,000-logo integration directory, and this page won't pretend otherwise. It has one mechanism built deeply - webhooks in and out, plus email and Slack - which in practice connects the tools founders actually run. Here's what works today, with step-by-step recipes.

What ships in V1

Inbound webhooks - any tool that can send an HTTP request can start an Chromoly workflow. Unique URL and signing secret per trigger; every request logged in run history.
Outbound webhooks - any workflow step can call an external API, with credentials stored encrypted and failed calls retried with backoff.
Email - transactional sends from workflows: reminders, digests, notifications.
Slack - alerts and messages to channels via your workspace's webhook URL.

Native integrations - inbound email, calendars, accounting tools - land after launch, built to the same no-silent-failure standard. Until then, these recipes cover the gap honestly.

Recipes

Typeform → Chromoly

Form submissions become leads, tickets, or applications - with AI scoring on arrival.

Stripe → Chromoly

Payment events update invoices, trigger onboarding, and flag failed charges.

Calendly → Chromoly

Bookings create CRM records and kick off meeting-prep workflows.

Shopify → Chromoly

Orders flow into inventory, fulfilment checklists, and ops dashboards.

HubSpot ↔ Chromoly

Sync contacts and deals between HubSpot and your internal systems.

Google Forms → Chromoly

The free-forms route, via a small Apps Script - full recipe included.

A tool not listed here almost certainly still works - the pattern in every recipe is the same: create a webhook trigger, paste the URL into the other tool, map the fields. The integrations documentation has the general mechanics.

Questions

What integrations does Chromoly support?

V1 ships four connection types: inbound webhooks (any tool can start an Chromoly workflow), outbound webhooks (any workflow step can call an external API), transactional email, and Slack messages. If the other tool speaks HTTP, Chromoly talks to it. Native integrations (inbound email, calendars, accounting) arrive after launch.

Why webhooks first instead of a big integration directory?

Honesty and reliability. Integration directories often mean hundreds of shallow connectors that break silently. Webhooks are one mechanism, deeply built: signing secrets, run history on every request, retries with backoff, and failures that alert instead of hiding.

Can Chromoly replace my Zapier or Make setup?

Often, yes - most automation stacks exist to move data between tools and a spreadsheet. Chromoly generates the system of record and runs the automation inside it. See vs Zapier and vs Make for where each wins.

Build the system this feeds

Describe it in plain language - the webhook trigger is part of the description. Preview free before anything deploys.

Start free