Service Integrations
Service integrations allow Lowgile applications to communicate with external platforms, APIs, AI services, databases, and messaging systems.
These integrations are commonly used to:
- Connect to external APIs and platforms,
- Send and process emails,
- Execute AI-driven workflows,
- Read or synchronize external data,
- Generate or process files and documents, and
- Automate communication between systems.
Integrations can execute automatically during workflows, background processing, scheduled jobs, services, scripts, or user-triggered actions.
How integrations work
Section titled “How integrations work”Most integrations in Lowgile follow a shared workflow pattern:
- Define a reusable configuration item that stores credentials, connection details, or runtime settings.
- Reference the configuration item from the workflow, service, automation, or script that requires the integration.
- Execute the integration during workflow or application processing.
- Exchange data with the external service or platform.
- Use the returned data to update records, trigger workflow transitions, generate output, or continue processing.
Service integration workflow pattern.
Integration architecture
Section titled “Integration architecture”Lowgile integrations are typically composed of:
- Configuration items for credentials and runtime settings,
- Workflows or processes that coordinate execution,
- Services or scripts that implement integration logic,
- Runtime actions that exchange external data, and
- Functional screens that expose integration functionality to users.
Together, these components support reusable, maintainable, and environment-aware integrations.
Common integration types
Section titled “Common integration types”The following integration types are frequently used in Lowgile applications.
1. AI services
Section titled “1. AI services”AI integrations are typically used to analyze or process unstructured content, including documents, emails, attachments, and generated output.
Typical AI integration scenarios include:
- Extracting data from uploaded documents,
- Processing emails and attachments,
- Generating summaries or structured output,
- Analyzing application data or content, and
- Executing AI-driven automation workflows.
These integrations commonly reference AI configuration items such as:
2. Email services
Section titled “2. Email services”Email integrations support both outbound communication and inbound processing.
Typical use cases include:
- Sending application-generated emails,
- Monitoring incoming email messages,
- Processing attachments,
- Triggering workflows from received emails, and
- Extracting structured information from email content.
3. External APIs
Section titled “3. External APIs”External API integrations are commonly used to:
- Exchange business data,
- Synchronize records between systems,
- Trigger external services, and
- Retrieve information from third-party platforms.
4. Database integrations
Section titled “4. Database integrations”Applications may integrate with external databases to:
- Read or synchronize external data,
- Import or export records,
- Support reporting and analytics workflows, and
- Share data between systems.
5. File and document services
Section titled “5. File and document services”Lowgile integrations can generate, process, store, or analyze files and documents.
Examples include:
- PDF generation,
- CSV and Excel processing,
- Document extraction,
- Attachment processing, and
- File storage services.
Configuration management
Section titled “Configuration management”Many integrations depend on reusable configuration items, often stored in the shared Common module.
These configuration items commonly store:
- API keys and credentials,
- Authentication settings,
- Service endpoints,
- Runtime settings, and
- Environment-specific configuration values.
Runtime execution
Section titled “Runtime execution”Integrations can execute automatically during workflows, background automation, scheduled jobs, email processing, or user-triggered actions.
During execution, integrations may:
- Synchronize external data,
- Trigger workflow transitions,
- Generate notifications, documents, or AI output, and
- Exchange information between systems.
Security considerations
Section titled “Security considerations”Sensitive integration values such as API keys, passwords, and credentials should be stored in configuration items rather than embedded directly inside workflows or code.
This allows:
- Centralized credential management,
- Safer environment configuration,
- Easier credential rotation, and
- Reduced duplication across the application.
Danger
Do not hardcode credentials, API keys, passwords, or environment-specific values directly inside workflows, scripts, services, or runtime logic.