How Integrations Work

Integrations in LightLead follow a unified approach regardless of the connected service type.

General Process

1. Authorization: user grants access via OAuth 2.0
2. Token retrieval: LightLead stores the access token for API requests
3. Data sync: periodic or on-demand requests to the service API
4. Normalization: data is converted to LightLead's unified format
5. Display: data is available in reports and dashboards

OAuth 2.0

Most integrations use OAuth 2.0:

• User authorizes on the service side
• LightLead receives an access token and refresh token
• Tokens auto-refresh on expiration

Data Caching

Data is cached to optimize performance:

• Hot data (last 7 days) refreshes more frequently
• Historical data is cached for longer periods
• Forced refresh is available via the "Refresh" button

Error Handling

• Automatic retry on temporary failures
• Exponential backoff on rate limiting
• Clear error messages in the interface

Related Pages

• Connection Statuses
• Multiple Connections
• Permissions