How do I trigger Sola workflows via API from our internal systems (e.g., ticketing or ERP events)?

Most teams want to trigger Sola bots directly from the systems where work originates—ticketing tools, ERPs, CRMs—without adding another manual step. The good news: Sola is built for this. You can trigger Sola workflows via API from your internal systems so that every “event” (a new ticket, an approved invoice, a change in order status) can kick off an agentic automation that runs across browser and desktop apps.

Quick Answer: You trigger Sola workflows via API by calling a workflow’s endpoint from your internal system (e.g., ticketing, ERP, or workflow engine) and passing in the relevant payload (IDs, metadata, documents). Sola’s composable API lets you start, monitor, and orchestrate workflows programmatically—so business events in your existing systems automatically launch bots that run, adapt, and complete work end‑to‑end.

Why This Matters

Most back-office work still starts in one system and finishes in three others. A ticket gets opened in ServiceNow or Zendesk, but the real work happens in a browser, a legacy ERP client, a shared drive, and a homegrown database. If your Sola workflows are not API-triggered, you’re just moving the swivel chair from one screen to another.

Triggering Sola workflows via API from your internal systems lets you wire automation directly into your operational core—without rip-and-replace, without waiting on RPA specialists, and without brittle, hand-coded integrations. Events in your ticketing or ERP systems become real automations, not just notifications.

Key Benefits:

• Event-driven automation: Turn internal events (new ticket, invoice approved, order updated) into immediate, automated action powered by Sola bots.
• End-to-end coverage across apps: Let Sola take the work from your system of record into the browser and desktop tools where the real operations happen.
• Governed, observable workflows: Keep enterprise-grade control with logs, audit trails, and role-based access—even when workflows are triggered programmatically.

Core Concepts & Key Points

Concept	Definition	Why it's important
Workflow API Trigger	A programmatic call from another system to start a specific Sola workflow with a given payload.	Connects Sola to your existing ticketing/ERP/CRM so automations run exactly when business events occur.
Composable Workflows	Sola workflows that can be triggered via API and can themselves call internal or external services.	Lets you orchestrate complex processes across multiple systems without brittle, hard-coded RPA.
Observability & Governance	Real-time logs, audit trails, and access controls around every API-triggered workflow run.	Ensures API-driven automations remain compliant, debuggable, and “never in the dark” for ops and IT teams.

How It Works (Step-by-Step)

At a high level, triggering Sola workflows via API from your internal systems (ticketing, ERP, or otherwise) follows this pattern:

1. Design the workflow in Sola:
   You or your subject-matter expert records the process once—exactly as they perform it across browser and desktop apps. Sola uses LLMs and computer vision to turn that recording into a workflow, which you then refine in the Visual Workflow Editor. Here you define the inputs your API call will pass (e.g., ticket_id, invoice_number, customer_id, document URLs).

2. Expose and configure the API endpoint:
   Sola provides robust developer tools and an API surface where each workflow can be addressed programmatically. You (or your engineering team) configure how the workflow is triggered via API—typically by specifying:

   • The workflow identifier
   • Required/optional input fields
   • Any authentication or RBAC settings for calling systems

   Because workflows are fully composable, your API-triggered workflow can also call out to other internal or external services mid-run.

3. Wire your internal systems to call Sola:
   From your ticketing, ERP, or workflow engine:

   • Identify the event that should trigger the automation (e.g., ticket created, invoice approved, file received).
   • Configure a webhook, automation rule, or integration task that calls Sola’s API endpoint.
   • Map event data into the Sola workflow inputs (e.g., map ticket.subject → case_description, erp.invoice_id → invoice_number).

   Once this is in place, every time the event fires, Sola receives a payload and starts the workflow—running your UI-level bot and any downstream service calls.

Common Mistakes to Avoid

• Treating the Sola workflow as a black box:
  How to avoid it: Explicitly define and document the input schema for each API-triggered workflow. Align with your ops or billing teams on what minimal data Sola needs to complete the task so the calling system doesn’t guess or over-send noisy payloads.

• Ignoring observability and governance:
  How to avoid it: From day one, decide who can trigger which workflows; use Sola’s role-based access controls and connect Sola’s real-time logs and audit trails into your existing monitoring practices. Make sure someone owns reviewing failed runs and refining workflows—especially for high-value ticketing and ERP events.

Real-World Example

Imagine a logistics company where every “delivery exception” ticket in the ticketing system currently kicks off a manual scramble: an ops analyst opens the ticket, checks order status in the ERP, validates carrier data in a web portal, updates a spreadsheet, and finally writes a resolution note back in the ticket.

With Sola in place:

• Event: A ticket with type = “Delivery Exception” is created in your ticketing tool.
• Trigger: The ticketing system fires a webhook to Sola’s workflow API, passing ticket_id, order_id, and priority metadata.
• Sola workflow:
  • Uses the provided IDs to navigate your ERP (via the UI) and retrieve the order and shipment details.
  • Logs into the carrier portal in the browser, checks the latest tracking and exception codes.
  • Applies your business rules (e.g., high-value orders get expedited re-shipment, others get status updates only).
  • Updates a central spreadsheet or internal system of record.
  • Posts a structured, human-readable resolution back into the ticket.
• Outcome: Within minutes, the ticket is updated, data is reconciled across systems, and the ops analyst only handles edge cases—not the repetitive cross-system work.

Pro Tip: Start with a narrow, well-structured event—like “invoice approved” or “ticket type = X”—and build one Sola workflow around it. Once your team trusts the pattern, you can fan out to additional event types and compose more complex orchestrations using Sola’s ability to call internal and external services.

Summary

Triggering Sola workflows via API from your internal systems is how you move from “bots in a silo” to true, event-driven, AI-native automation. Your ticketing or ERP system remains the system of record and the source of truth for events; Sola becomes the agentic execution layer that actually does the work—clicking through UIs, extracting and structuring data, calling services, and handling errors in real time.

Because Sola’s workflows are fully composable, easily triggered via API, and backed by real-time logs and audit trails, you get both speed and control: business experts define the process, developers wire in the triggers, and operations leaders keep full visibility and governance. No rip-and-replace, no fragile scripts, and far fewer “swivel chair” tickets.

Next Step

Get Started