Add Integration Artifacts
Integration artifacts are the building blocks of every integration. Each type is designed for a specific trigger and communication pattern: receiving HTTP requests, reacting to messages, processing files, running on a schedule, or serving AI agent tools. Choosing the right artifact for the job keeps your integration logic focused and your project easy to navigate — this is the same picker, with the same categories and icons, that you see when you add a new artifact in the editor.
Automation
Run integration logic on a schedule or manually, without a network listener.
Durable Workflow
Design long-running workflow logic that can be interrupted by events, use timers, involve human tasks, and run with crash recovery.
AI Integration
Build AI-powered integrations that use large language models to reason, respond, and act.
Integration as API
Expose your integration logic as a callable endpoint. Clients send a request and receive a response.
Event-Driven Integration
React to messages or events produced by external systems. The integration runs when something happens, not when a client calls it.
File-Driven Integration
Trigger an integration when files appear on a remote server or local directory.
Supportive Artifacts
Reusable building blocks shared across multiple integrations in the same project.
What's next
- Automation — run scheduled or on-demand integration jobs
- HTTP service — the most common starting point for integration APIs
- Kafka — consume and process messages from Apache Kafka
- FTP/SFTP — process files from remote file servers
- Connections — connect to external systems once and reuse across your integration