For developers & integrators

Build a workflow. Test it safely. Run it where your customer needs it.

Connect the systems your customer already uses, describe the work in YAML and operate the result from your own assistant. titop.ai works with integrators through guided technical engagements with human approval before anything goes out.

01 · What you can plug in

Start with the systems your customer already has.

Keep the mailbox, CRM, calendar and documents in their current environment. Use the available connectors or discuss a custom integration through the adapters SDK.

View the supported integrations

Email

Available

Gmail / Google Workspace, Outlook / Microsoft 365, or any mailbox through IMAP / SMTP or forwarding.

CRM

Available

Odoo, HubSpot and Salesforce, without replacing the customer’s daily tools.

Calendars

Available

Outlook Calendar and Google Calendar within the access scope agreed for the environment.

Document stores

Private beta

Connect document stores as part of a scoped integration; we confirm the repository and access requirements with you.

Billing

Design partners

A read-only Stripe reference adapter shows how invoice state can support a workflow without changing billing data.

Your own credentials

Private beta

Use your own provider credentials within the access scope agreed for your tenant.

Connect your own system

The adapters SDK and reference packages are available to design partners on request, with integration scope confirmed during technical evaluation.

  • Use a provider-neutral contract for CRM, LLM, calendar or billing integrations.
  • Make the integration discoverable by the platform through the SDK plugin model.
  • Check compatibility with the supplied contract tests before activation.

02 · How you describe a workflow

One readable YAML document, on an open standard.

Describe a workflow in YAML based on CNCF Serverless Workflow 1.0. Work with familiar concepts such as triggers, actions, conditions, approvals, waits and loops.

01

Validate the document with the schema package before reviewing it for a customer environment.

02

Read every library workflow as a BPMN diagram as well as YAML, so technical and business reviewers can discuss the same flow.

03

Agree runtime, provider and access choices separately for each customer environment.

The template schema package is available to design partners on request.

03 · How you test it before anything goes out

Rehearse the whole exchange in a controlled environment.

Run a workflow end to end with scripted actors instead of experimenting on a customer. Review the outcome, compare it with what you expected and reset before another run.

Private beta

Scenario runs are exercised with our integrators in a controlled environment. Nothing in a captured run needs to leave that environment.

  • 01 Exercise the complete exchange with captured scenario runs.
  • 02 Review health per run and a redacted expected-versus-actual comparison.
  • 03 Reset captured test data when the run is finished.
  • 04 Use test mode for connectors and contract tests for custom integrations.
  • 05 Check template compatibility before activation.

04 · How you operate it from your own assistant

Use MCP to work with granted workflows and runs.

Private beta

Connect your own assistant to the MCP endpoint supplied for your tenant. Work with four focused tool families while access follows the member’s role and grants.

Templates

Review the workflows available to you and request publication of a change.

Traces

Inspect redacted run history and execution health without message payloads.

Scenarios

Start and advance a captured test run, then review its status.

Solutions

Browse solution cards with their outcomes, maturity and requirements.

  • Authentication uses the member’s own role and template grants.
  • Publication requires owner approval; the current version keeps running until then.
  • Operations are audited, and trace responses are redacted.

05 · Where it runs

Choose the deployment boundary with your customer.

Use our Swiss service or plan a deployment inside the customer’s own environment. Data stays within the agreed boundary, and a person approves outbound actions.

Available

Swiss SaaS

Run in titop’s Swiss SaaS environment with the deployment and access scope agreed for your tenant.

Private beta

On-prem bundle

Deploy the release bundle on your hardware in a scoped engagement, with release verification and setup agreed with our team.

In design

Your own cloud

Run the stack inside your own cloud subscription when your deployment must remain within your own cloud boundary.

Human approval remains part of the operating model in every deployment: outbound actions and publication wait for the designated approver.

06 · Get access

Bring one customer workflow to the private beta.

We onboard integrators and design partners through a guided technical engagement. Start with one concrete workflow, one environment and clear acceptance criteria.

Book a developer demo Contact the developer team
  • A sandbox tenant for evaluation
  • The developer and reference packages on request
  • An MCP endpoint and a scoped set of grants
  • A named technical contact for integration and deployment questions