## What Connectors Do (and Don't Do) Connectors are the bridges between Lucky Desk and the other tools your business runs on. An ERP for accounting, a CRM for sales, an email platform for marketing, a warehouse system for logistics — connectors keep data flowing between these systems without manual re-entry. What connectors do: - Sync data between Lucky Desk and external systems (bidirectional or one-way) - Map fields between different data structures - Handle authentication and API communication - Monitor sync health and alert on failures - Transform data formats when systems disagree on structure What connectors don't do: - Replace your existing tools (they connect them) - Magically resolve data quality issues (garbage in, garbage out) - Work without configuration (you need to tell them what to sync and how) Think of connectors as translators that keep two systems speaking the same language. They're powerful, but they need clear instructions. ## How Connectors Work in Lucky Desk Every connector follows the same pattern: **1. Authentication.** Connect your external account — usually via OAuth (click "Connect" and authorize), API key, or webhook URL. This is a one-time setup per connection. **2. Entity mapping.** Define which data objects map to each other. "Customers in my CRM" maps to "Organizations in Lucky Desk." "Products in my ERP" maps to "Items in Lucky Desk." Not everything needs to sync — only the entities that benefit from being in both systems. **3. Field mapping.** Within each entity, define which fields correspond. The CRM's "Company Name" maps to Lucky Desk's "Organization Name." The ERP's "Article Number" maps to "Product SKU." Some fields map directly; others need transformation (splitting a full name into first/last, converting currencies, reformatting dates). **4. Sync rules.** Define the direction and frequency. Does data flow from the CRM to Lucky Desk, from Lucky Desk to the CRM, or both ways? Does it sync in real-time (via webhooks), on a schedule (every 15 minutes), or on demand (manual trigger)? **5. Conflict resolution.** When both systems have changed the same record, which one wins? Options include: most recent change wins, source system always wins, or flag for manual review. For most setups, designating one system as the "source of truth" for each data type avoids conflicts entirely. ## Common Integration Patterns ### Pattern 1: CRM Sync **Scenario:** Your sales team uses a CRM (HubSpot, Pipedrive, Salesforce). Your operations team uses Lucky Desk. Both need customer data. **Setup:** Sync contacts and companies bidirectionally. New contacts created in either system appear in the other. Updates to phone numbers, addresses, and key fields sync automatically. **Best practice:** Let the CRM be the source of truth for sales-related fields (deal value, pipeline stage, last contact date). Let Lucky Desk be the source of truth for operational fields (order history, support tickets, service records). This avoids conflicts by giving each system ownership of its domain. ### Pattern 2: Accounting Push **Scenario:** Invoices are generated in Lucky Desk based on completed work or orders. Your accounting system (Exact, Xero, QuickBooks) needs these invoices for bookkeeping. **Setup:** One-way sync from Lucky Desk to accounting. When an invoice is finalized in Lucky Desk, the connector creates the corresponding invoice in the accounting system with all line items, tax rates, and customer details. **Best practice:** Don't sync back payment status for the first implementation. Get invoice creation working reliably, then add payment status sync in a second phase. Trying to do everything at once leads to a more complex setup that's harder to debug. ### Pattern 3: E-commerce Inventory **Scenario:** You sell products through an online store (Shopify, WooCommerce). Stock levels in Lucky Desk need to reflect on the webshop. **Setup:** Inventory levels sync from Lucky Desk (source of truth) to the e-commerce platform. Orders from the e-commerce platform sync to Lucky Desk for fulfillment. Product information (descriptions, prices, images) syncs from Lucky Desk to the store. **Best practice:** Inventory sync should be near-real-time to avoid overselling. Product data sync can be less frequent. Order sync should be immediate so fulfillment isn't delayed. ### Pattern 4: Email Marketing **Scenario:** You use Mailchimp, Brevo, or ActiveCampaign for email campaigns. Contact lists should reflect your Lucky Desk customer data. **Setup:** One-way sync of contacts from Lucky Desk to your email platform. Segment information (customer type, industry, location) translates to email list tags or segments. **Best practice:** Sync opt-in status carefully. If a contact opts out of emails in your marketing platform, that preference should be respected. Don't accidentally re-subscribe people by overwriting their opt-out with a sync. ## Setting Up Your First Connector **Step 1: Pick the integration that saves the most manual work.** Usually it's the system where your team spends the most time re-entering data that already exists somewhere else. **Step 2: Start with one entity.** Don't try to sync everything at once. Pick the most important data type (usually contacts/customers) and get that working first. **Step 3: Map fields conservatively.** Only map fields you actually need in both systems. Every mapped field is a potential point of failure. Start with 5-10 essential fields, not 30. **Step 4: Run in "preview" mode.** Most connectors let you see what would sync before actually syncing. Review the first batch of records to check that the mapping produces correct results. **Step 5: Sync a small batch.** Sync 10-20 records and verify them manually in both systems. Check that fields populated correctly, relationships are maintained, and nothing unexpected happened. **Step 6: Enable automatic sync.** Once you're confident in the mapping, enable scheduled or real-time sync. Monitor the sync dashboard for the first week to catch any issues. ## Troubleshooting Common Issues **"Records aren't syncing."** Check authentication — API keys expire, OAuth tokens need refreshing. Check the sync log for error messages. Most sync failures are authentication timeouts or rate limit errors. **"Data looks wrong after sync."** Usually a field mapping issue. Common culprits: date format differences (US vs. European), currency fields syncing without conversion, text fields truncated because the target system has a character limit. **"Duplicates appearing."** The connector can't find the matching record in the target system, so it creates a new one. Solution: define a reliable matching key (email address for contacts, product code for items) and ensure it's populated in both systems. **"Sync is slow."** Large initial syncs (thousands of records) take time. Subsequent incremental syncs should be fast. If ongoing syncs are slow, check if you're syncing too many fields or triggering unnecessary recalculations in the target system. ## When to Use Connectors vs. API Connectors are the right choice when: - You need ongoing, automated data sync between systems - The integration pattern is common (CRM sync, accounting push) - You want a visual configuration interface without writing code - You need monitoring and error handling built in The API is the right choice when: - You need custom logic that connectors don't support - You're building a unique integration specific to your business - You need real-time event handling with complex processing - You have development resources available Many businesses use both: connectors for standard integrations and the API for custom workflows that don't fit a standard pattern. ## Available Connectors Lucky Desk's connector library covers the most common business tools. New connectors are added regularly based on customer demand. If your tool isn't listed, check whether it offers a generic API or webhook that can be connected through our universal API connector. Your first connector should be the tool where duplicate data entry causes the most friction. Start there, prove the value, and expand your integration landscape one connection at a time.