How it works

You want to build an integration. Now what?

Build

Describe the job. Specc builds the steps.

What it usually takes

  • Pay a developer.Hire one, pay an agency or take someone off your own product.
  • Find the documentation.It may be spread across pages, out of date or silent about the fields you need.
  • Understand the systems.Each system names things differently, records depend on each other, and real data doesn't always match the docs.
  • Write the code.Read, change and send the data, then handle missing fields, large lists and rejected requests.

With Specc

Tell Specc which systems to connect and what should happen. Its AI builder works through the documentation, the real data and test results to build the integration.

The result is a saved set of steps you can inspect and refine: what to read, how to change it and where to send it. Renaming fields, converting formats, matching records, filtering and combining data are steps like any other.

You provide access to your systems and decide what the integration should do.

For exampleThe shop and the accounting system use different customer numbers. Finding the matching customer before creating the invoice becomes one of the steps.

Deploy

Choose what runs. Set it up for each customer.

What it usually takes

  • Deploy the integration.It needs somewhere to run, a way to start on time and secure access to the systems it connects.
  • Customize it for each customer.Different accounts, settings and needs, kept apart, while you keep track of who runs which version.

With Specc

Connect the accounts the integration uses, fill in its settings, then test it and inspect the results. You choose which saved version goes into use and when it starts.

Every change is saved as a new version, and every run records the version it used. You can point to the exact steps that ran.

Serving several customers?

Install the same integration for each one. Every installation has its own copy of the steps, connections, settings and run history, and permissions control who can manage it. Review a change and decide which customers should get it.

For exampleTwo customers use the same systems. One needs different tax codes and an extra field; the other keeps their current setup.

Maintain

See what happened. Decide what to fix.

What it usually takes

  • Make sure it keeps running.A server can look healthy while half the records are rejected.
  • Fix it when systems change.A field changes or an old request is removed, and the integration stops working although nobody touched your code.
  • Debug what was sent, what wasn't and why.Hours in the logs, then deciding what is safe to send again without creating duplicates.

With Specc

Integrations run their saved steps on a schedule or when an event you set up starts them, without an AI conversation. Activity shows run status, the outcome for each record and the available execution details.

When work fails, inspect the requests, replies and data around it. Where an action tracks its result, a confirmed result is reused instead of being sent again. If the other system doesn't confirm whether it saved the data, the result is marked uncertain and is not retried without checking.

Self heal is opt-in.

When you turn it on, it investigates failed runs, groups related issues and proposes the next step: a change to the integration, renewed access or corrected source data. You decide whether to apply it, then choose separately which work to retry.

For exampleAn invoice request timed out. Specc marks the result uncertain, so you can check whether the invoice exists before anything is sent again.

Which systems do you need to connect?

Tell us where the data is, where it needs to go and what should happen along the way.