Integrations

Lotics connects to the tools your team already uses so data flows between systems without manual re-entry. Every integration is built on the same principles: OAuth or secure API keys for authentication (Lotics never stores passwords), bidirectional sync so both systems stay current, and full exposure as workflow triggers and actions so you can automate across tools without code.

Integration philosophy

Connected accounts are organization-scoped. When one team member connects their Gmail or Google Drive, workflows created by anyone in the organization can use that connection. One person authorizes, the entire team benefits.

All integrations are managed from Settings > Connected Accounts. Each connected account shows its status, the team member who authorized it, and which workflows use it. The AI assistant can also guide you through connecting accounts: describe what you want to automate and it will walk you through the OAuth flow and set up the workflow for you.

Every integration works in both directions. Changes in Lotics push to connected systems (send an email, create a file, issue an invoice). Events from external systems trigger workflows inside Lotics (incoming email, new file in folder, customer message, bank transaction). This bidirectional sync means Lotics becomes the central hub where all your operational data converges.

Email: Gmail and Outlook

Connect your Gmail or Microsoft Outlook account via OAuth. Once connected, you can send emails directly from Lotics, either manually through the AI assistant or automatically through workflows. Emails are sent from your actual email address, so recipients see messages from you, not from a generic system address.

Incoming email triggers

When a new email arrives matching your criteria (sender, subject, labels), Lotics starts a workflow automatically. The workflow receives the full email: subject, body, sender, and attachments. AI steps can then extract data from attachments, create or update records, and route work to the right team members.

Example: A supplier sends an invoice by email. Lotics detects the email, the AI extracts line items from the attached PDF, creates records in your invoices table, cross-checks quantities and prices against the corresponding purchase order, flags discrepancies, and notifies your finance team. No one needs to open the email manually.

Outgoing email actions

Workflow steps can compose and send emails using data from records and previous steps. Common patterns include order confirmations, payment reminders, document delivery (attach a generated PDF to the email), and follow-up sequences triggered by status changes.

Cloud storage: Google Drive and OneDrive

Connect Google Drive or Microsoft OneDrive to access files stored in your cloud drives. Workflows can read documents from specific folders, process them with AI, and write results back. File attachments on records can be synced to designated folders so your existing file organization stays intact.

Reading and processing documents

For teams that manage contracts, certificates, or compliance documents in shared drives, this integration means Lotics can pull the latest version of a document, extract key dates or values with AI, and update records automatically.

Triggering on new files

When a new document appears in a monitored folder, a workflow can trigger to process it. This is useful for teams that receive documents from external parties via shared folders (shipping documents, customs declarations, signed contracts).

SharePoint support

SharePoint document libraries are supported through the OneDrive integration. Organizations on Microsoft 365 can connect their team sites directly without additional configuration.

Messaging: Zalo and Facebook

Zalo Official Account

Zalo is the dominant messaging platform in Vietnam. Lotics integrates with Zalo Official Account (OA) so businesses can communicate with customers directly from workflows:

• Outgoing: Send notifications to customers, including order confirmations, delivery updates, appointment reminders, and payment receipts
• Incoming: Receive customer inquiries and messages, then trigger workflows to route, respond, or create records automatically
• Templates: Send structured template messages with data pulled from records (order status with tracking number, delivery ETA with address)

Facebook Page

Connect your business page and Lotics can send messages through it, receive customer inquiries, and trigger workflows when new messages arrive. For businesses that handle customer communication through Facebook Messenger, inquiries flow into Lotics automatically and can be tracked, assigned, and responded to alongside other operational work.

Both Zalo and Facebook integrations support template messages with structured data from records, so notifications look professional and include the specific information your customers need.

Vietnamese business platforms

Vietnamese businesses operate under specific regulatory and infrastructure requirements: electronic invoicing for tax compliance, domestic banking integrations for payment reconciliation, and QR-based payment standards. Lotics integrates with the platforms that handle these requirements natively.

End-to-end payment example

These integrations are particularly valuable when combined. A workflow can issue an electronic invoice in WinInvoice when a sales record is marked complete, generate a VietQR code for the customer to pay, send the QR code via Zalo or email, and then match the incoming bank transaction from Vietcombank to close the loop automatically. The entire cycle from invoice to confirmed payment is tracked in one place with no manual data entry.

Webhooks

For systems that Lotics does not integrate with directly, webhooks provide a universal connection point.

Incoming webhooks

Each webhook trigger in a workflow gets an auto-generated HTTPS URL. Any external system that can send an HTTP POST request (ERPs, e-commerce platforms, IoT devices, custom applications) can trigger a Lotics workflow by posting JSON data to that URL.

The incoming webhook payload is available as structured data inside the workflow. You can extract fields, create or update records, run AI processing, and trigger follow-up actions. Signature verification is supported so you can validate that requests come from trusted sources.

Outgoing webhooks

Outgoing webhooks work as workflow actions. When a record changes or a workflow reaches a specific step, Lotics sends an HTTP POST with event data to your endpoint. This keeps external dashboards, data warehouses, or legacy systems in sync with your Lotics data.

Coming soon

Lotics is actively expanding its integration library. The platform is not limited to the integrations listed above — any category of software can be connected. Upcoming and planned integrations include:

• Accounting — QuickBooks, Xero, MISA, Fast Accounting
• CRM — Salesforce, HubSpot, Zoho CRM
• E-commerce — Shopify, WooCommerce, Lazada, Shopee
• ERP — SAP, Odoo, Oracle NetSuite
• Project management — Jira, Asana, Monday, Linear, Trello
• Cloud infrastructure — AWS, Google Cloud, Azure
• Developer tools — GitHub, GitLab, Slack, Discord
• Logistics — shipping line APIs, customs portals, freight marketplaces
• HR & Payroll — BambooHR, Gusto, local payroll systems
• Communication — Telegram, WhatsApp Business, SMS gateways

New integrations are added regularly based on customer needs. If you need a specific integration, contact the Lotics team — custom connections can often be built quickly.

In the meantime, webhooks and the REST API provide universal connectivity for any system that can send or receive HTTP requests. Most integrations can be achieved today through webhook-based workflows without waiting for a native connector.

REST API

The Lotics API gives you full programmatic access to everything in your workspace: tables, records, views, workflows, document templates, files, and connected accounts. The API follows REST conventions with JSON request and response bodies. An OpenAPI 3.1.0 specification is published at https://api.lotics.ai/v1/openapi.json.

API keys are created in Settings > API Keys and scoped to a single organization. See the REST API documentation for authentication details, available endpoints, rate limits, and code examples.

Frequently asked questions

Does Lotics store my email password or cloud storage credentials?

No. All integrations use OAuth 2.0 authorization. Lotics receives a scoped access token, never your password. You can revoke access at any time from your Google, Microsoft, or platform account settings.

Can multiple team members connect their own accounts?

Yes. Each team member can connect their own Gmail, Outlook, or other accounts. Workflows specify which connected account to use, so you control which emails are sent from which address.

What happens if a connected account token expires?

Lotics automatically refreshes OAuth tokens before they expire. If a refresh fails (for example, the user revoked access), the workflow step will fail with a clear error and the connected account will show as disconnected in Settings so you can re-authorize.

Can I use webhooks to connect Lotics to my ERP?

Yes. Set up a webhook trigger in a Lotics workflow to receive events from your ERP. The ERP sends an HTTP POST with the event data (new order, stock update, shipment status) and Lotics processes it automatically. You can also send data back to your ERP using outgoing webhook actions in workflows.

Are Vietnamese platform integrations available on all plans?

Yes. WinInvoice, Vietcombank, VietQR, and PayOS integrations are available on all Lotics plans. Setup involves connecting your business account in Settings > Connected Accounts, and the AI assistant can guide you through the process.

What if I need an integration that is not listed here?

Lotics is actively building more integrations based on customer needs. For any system not directly supported, webhooks and the REST API provide universal connectivity: any tool that can send or receive HTTP requests can exchange data with Lotics. Contact the Lotics team to discuss your requirements.