Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/ency07/B2B-import/llms.txt

Use this file to discover all available pages before exploring further.

The Integrations module connects B2B Import ERP to the external services your business relies on. Every integration is configured per tenant from the dashboard; credentials are stored securely in the database and never in application environment files. Each provider has an is_active flag so you can enable or disable it at runtime without touching code or triggering a redeployment.

​
Integration Categories

​
Email Providers

SMTP (Custom)

Any SMTP server. Configure host, port, username, password, and TLS settings. Suitable for self-hosted mail servers or enterprise relays.

Resend

Modern transactional email API. Recommended for high deliverability and built-in open/click analytics.

SendGrid

Industry-standard email delivery platform. Supports templates, suppression lists, and send-time optimization.

Amazon SES

High-volume, low-cost email delivery. Ideal for tenants already running infrastructure on AWS.

Mailgun

Developer-focused email API with powerful log and analytics features.

​
Messaging

WhatsApp — Twilio

Send transactional and notification messages over WhatsApp Business API via the Twilio channel. Configurable per-tenant account SID and auth token.

WhatsApp — Meta / 360dialog

Direct integration with the Meta WhatsApp Business API via 360dialog. Supports rich messages and interactive buttons.

Telegram

Bot Token, target Chat IDs, channels, groups, and individual user priorities. All recipients are stored in the database — no hardcoded chat IDs.

SMS — Twilio

SMS delivery globally via Twilio. Configurable sender number per use case (sales, support, emergencies).

SMS — Vonage

Alternative SMS provider with strong coverage in Latin America.

​
AI / LLM Providers

AI providers power optional features such as catalog natural-language chat and future engineering analysis enhancements. The lead wizard and scoring engine are deterministic and do not use AI.

OpenAI

GPT-4o and later models. Requires API key stored per tenant.

Anthropic

Claude models. Configurable model version and max tokens.

Google Gemini

Gemini Pro and Ultra. Requires Google Cloud project API key.

DeepSeek

Open-weight model with strong code and technical reasoning capabilities.

Groq

Ultra-low-latency inference for Llama and Mixtral models.

Ollama

Self-hosted open-source models. Requires a running Ollama instance accessible from the server.

Azure OpenAI

Enterprise-grade OpenAI deployment on Azure infrastructure. Configures endpoint URL, deployment name, and API version.

​
Payment Gateways

Wompi

Primary gateway for Colombia. Supports PSE (bank transfer), credit/debit cards, Nequi, Bancolombia QR, and cash at Efecty. Requires public key and private key per tenant.

Stripe

Global card processing with support for subscriptions, invoices, and saved payment methods. Recommended for tenants operating internationally.

MercadoPago

Dominant payment platform across Latin America. Supports multiple local payment methods beyond cards.

PayPal

Global payment platform. Configurable per tenant with client ID and secret key.

​
Storage Providers

Supabase Storage

Default bucket provider. Used for tenant logos, PDF attachments, and document assets. Buckets are isolated per tenant.

Amazon S3

High-durability object storage. Configurable bucket name, region, access key, and secret key per tenant.

Cloudflare R2

S3-compatible object storage with zero egress fees.

Azure Blob Storage

Enterprise blob storage for tenants on Azure infrastructure.

Backblaze B2

Cost-effective cloud storage compatible with the S3 API.

​
Maps

Google Maps

Geocoding, address autocomplete, and map embeds. Requires a Google Maps API key per tenant.

Mapbox

Customizable vector maps. Configurable access token per tenant.

OpenStreetMap

Open-source mapping platform. No API key required.

​
Calendar Integrations

Google Calendar

Sync work orders and scheduled jobs with Google Calendar. Requires OAuth 2.0 credentials stored per tenant.

Microsoft Calendar

Integration with Microsoft 365 / Outlook Calendar via the Graph API.

​
Webhooks

Inbound Webhooks

Receive events from external systems. Each tenant can configure endpoint paths and validation secrets independently.

Outbound Webhooks

Push B2B Import ERP events (invoice created, job completed, etc.) to external URLs. Configurable per event type and destination.

​
Configuration Pattern

All credentials, API keys, webhook URLs, and phone numbers are stored as encrypted rows in the tenant_settings table under the INTEGRACIONES and TELEFONIA modules. The INTEGRACIONES and TELEFONIA module constraints are added to tenant_settings by migration 20260617000033_integrations.sql. The only values that live in environment files are the server bootstrap secrets required before the database is accessible (e.g., SUPABASE_SERVICE_ROLE_KEY, NEXT_PUBLIC_SUPABASE_URL). This means:
  • Adding or rotating a WhatsApp number requires a dashboard update, not a code change or redeployment.
  • Rotating an API key is an instant database update.
  • White-label tenants each configure their own provider credentials independently.

​
Telephony Numbers

All contact numbers are stored as individual keys in the TELEFONIA module. Defined keys include: numero_ventas, numero_soporte, numero_emergencias, numero_garantias, numero_facturacion, numero_administrativo, numero_gerente, numero_tecnico, numero_whatsapp, numero_llamadas, numero_sms. The database enforces E.164 international format (+573001112233) on every phone number value via the validate_tenant_settings_white_label trigger.

​
Notification Routing

The notification_routes key in INTEGRACIONES is a JSONB object that maps system events to their delivery channels and recipient roles: 
{
  "invoice_overdue": {
    "roles": ["GERENTE", "COORDINADOR"],
    "channels": ["EMAIL", "WHATSAPP", "TELEGRAM"]
  },
  "lead_created": {
    "roles": ["VENTAS"],
    "channels": ["IN_APP", "EMAIL"]
  }
}
The dispatch_notification_to_route() database function resolves this configuration at runtime: it looks up all users with the specified roles in the tenant, checks each user’s notification_preferences to honor opt-outs, and inserts pending delivery records into the notifications table. The execute_automation_rules() function calls this dispatcher as part of the Phase 34 automation engine. Every event, channel, and recipient list is configurable from the dashboard without touching code.
Secrets stored in the tenant_settings table with is_encrypted = true are encrypted at rest using pgp_sym_encrypt (the pgcrypto PostgreSQL extension). Decryption happens transparently inside the get_tenant_setting() database function at read time. Never log config values from the INTEGRACIONES module or include them in API responses — the decrypted plaintext must only be used server-side at the moment of making an outbound API call.

​
Dashboard URL

/dashboard/settings?tenant=<code>
Integrations are managed from the Integrations tab within the Settings module. Each provider card shows its current is_active status and a masked preview of the stored API key.

Build docs developers (and LLMs) love

Get started for freeTalk to us