The approaches

Around the software, or inside it.

Connecting services and integrating agents into a product address different needs. The distinction lies in where rules, permissions and actions live.

Explore

Connect services.

Workflow tools chain operations across applications: receive a form, call an API, write a result, send a notification. This approach suits information moving between services.

Tools such as n8n, LangGraph or Dify can take part in different architectures. The choice depends on what you are building, available integrations and where business rules live.

Put the agent to work inside the product.

In an application designed with Syrtis, the tools offered to the agent belong to the software. They apply the same permissions and business logic as the team’s screens.

The agent carries the reasoning. The application owns the action, approval and history. A product event can start the process without a conversation.

Start from the process you want to improve.

If the need is to move data across existing services, an automation may be enough. If the agent must act within a product under its user’s permissions, that contract needs to be defined at application level.

Two architectural scopes
The scopeBetween servicesInside the product with Syrtis
TriggerAn event or a service callEvent, process, button or conversation
Business rulesCoordinated with each connected serviceApplied in the application
ActionService APIs and connectorsBusiness tools with permissions and history
ResultSent to the relevant serviceAttached to the product record or process

It starts with
one process.

The one your team does by hand, every week.
What if your software took care of it?