How to Integrate Lovable with Freshsales

Freshsales uses API key authentication, similar to Pipedrive. Each user has a personal API key that provides access to the API with that user's permissions. To get your API key: log in to Freshsales and click your profile avatar in the top-right corner. Select 'Profile Settings' from the dropdown. In the Profile Settings page, scroll to the 'API Settings' section. Your API key is displayed — click the eye icon to show it and copy it. Your Freshsales subdomain is the company name part of your Freshsales URL. When you log in, the URL looks like yourcompany.freshsales.io. The subdomain is 'yourcompany' (without .freshsales.io). This forms the base URL for all API calls: https://yourcompany.freshsales.io/api/. Freshsales API base URL format: https://{subdomain}.freshsales.io/api/ Example endpoint: https://yourcompany.freshsales.io/api/contacts Authentication header: Token token={YOUR_API_KEY} Note the 'Token token=' prefix — this is Freshsales-specific and different from 'Bearer' or 'Basic' auth formats. Forgetting the 'Token token=' prefix causes 401 errors even with a valid API key. For production integrations, consider using the API key of a dedicated admin user rather than your personal account, so the integration is not disrupted if your account permissions change.

Add Freshsales credentials to Lovable's Cloud Secrets panel. In Lovable, click '+' → Cloud panel → Secrets tab. Add two secrets: - FRESHSALES_API_KEY — your personal API key from Freshsales Profile Settings - FRESHSALES_SUBDOMAIN — your Freshsales subdomain (just 'yourcompany', not the full URL) The Edge Function constructs the full API base URL as: https://${FRESHSALES_SUBDOMAIN}.freshsales.io/api/ Store the subdomain without protocol or domain suffix. Including 'https://' or '.freshsales.io' creates malformed URLs. Freshsales API authentication header format is: Token token=YOUR_API_KEY — note the capital T in 'Token' and the lowercase 'token=' prefix before the key value. This double-token format is specific to Freshsales and does not follow the standard Bearer token convention. The Freshsales API supports JSON responses for all endpoints. All list endpoints return data in a named array matching the resource type: contacts returns { contacts: [...] }, deals returns { deals: [...] }. Single resource endpoints return the object directly: { contact: {...} }. Pagination uses page and per_page query parameters with a default of 25 items per page.

Build the Edge Function that handles common Freshsales operations. The Freshsales API uses standard REST conventions with JSON request/response bodies and query parameters for filtering and pagination. Key Freshsales API endpoints: - Contacts: GET /api/contacts (list), GET /api/contacts/{id} (get), POST /api/contacts (create), PUT /api/contacts/{id} (update) - Deals: GET /api/deals (list), POST /api/deals (create), PUT /api/deals/{id} (update) - Accounts: GET /api/accounts (list/search), POST /api/accounts (create) - Activities: GET /api/activities (list), POST /api/activities (create) Freshsales supports field filtering with the 'include' parameter to reduce response payload size: GET /api/contacts?include=freddy_score,last_activity_date returns only those fields plus the default ID and name fields. For searching contacts by email (the most common lookup): GET /api/contacts/filter uses POST with a filter body: { filter_rule: [{ attribute: 'email', operator: 'is_in', value: 'user@example.com' }] }. This endpoint requires a POST with the filter body even though it is a search/read operation. Freddy AI scores for contacts are available as the 'freddy_score' field (0-100). Deal health scores are 'freddy_forecast_score'. These fields are not returned by default — include them explicitly in the 'include' parameter.

1import { serve } from 'https://deno.land/std@0.168.0/http/server.ts'
2
3const corsHeaders = {
4  'Access-Control-Allow-Origin': '*',
5  'Access-Control-Allow-Headers': 'authorization, x-client-info, apikey, content-type',
6}
7
8function fsHeaders() {
9  const key = Deno.env.get('FRESHSALES_API_KEY')
10  if (!key) throw new Error('FRESHSALES_API_KEY not configured')
11  return {
12    Authorization: `Token token=${key}`,
13    'Content-Type': 'application/json',
14  }
15}
16
17function fsUrl(path: string) {
18  const sub = Deno.env.get('FRESHSALES_SUBDOMAIN')!
19  return `https://${sub}.freshsales.io/api${path}`
20}
21
22serve(async (req) => {
23  if (req.method === 'OPTIONS') return new Response('ok', { headers: corsHeaders })
24
25  try {
26    const { action, params = {} } = await req.json()
27    const headers = fsHeaders()
28    let resp: Response
29
30    switch (action) {
31      case 'create_contact':
32        resp = await fetch(fsUrl('/contacts'), {
33          method: 'POST',
34          headers,
35          body: JSON.stringify({
36            contact: {
37              first_name: params.firstName,
38              last_name: params.lastName,
39              email: params.email,
40              mobile_number: params.phone || '',
41              company: { name: params.company || '' },
42              lead_source_id: params.leadSourceId,
43              tags: params.tags || [],
44            },
45          }),
46        })
47        break
48
49      case 'list_contacts':
50        resp = await fetch(fsUrl(`/contacts?page=${params.page || 1}&per_page=${params.perPage || 25}&include=freddy_score,last_activity_date,deal_stage`), { headers })
51        break
52
53      case 'search_contact_by_email':
54        resp = await fetch(fsUrl('/filtered_search/contact'), {
55          method: 'POST',
56          headers,
57          body: JSON.stringify({
58            filter_rule: [{ attribute: 'email', operator: 'is_in', value: params.email }],
59          }),
60        })
61        break
62
63      case 'create_deal':
64        resp = await fetch(fsUrl('/deals'), {
65          method: 'POST',
66          headers,
67          body: JSON.stringify({
68            deal: {
69              name: params.name,
70              amount: params.amount,
71              contacts_added_list: params.contactId ? [params.contactId] : [],
72              deal_stage_id: params.dealStageId,
73              expected_close: params.expectedClose,
74            },
75          }),
76        })
77        break
78
79      case 'list_deals':
80        resp = await fetch(fsUrl(`/deals?page=${params.page || 1}&per_page=${params.perPage || 25}&include=freddy_forecast_score,contacts,deal_stage`), { headers })
81        break
82
83      case 'log_activity':
84        resp = await fetch(fsUrl('/activities'), {
85          method: 'POST',
86          headers,
87          body: JSON.stringify({
88            activity: {
89              title: params.title,
90              type: { name: params.type || 'Task' },
91              notes: params.notes || '',
92              targetable_type: 'Contact',
93              targetable_id: params.contactId,
94              due_date: params.dueDate || new Date().toISOString().split('T')[0],
95            },
96          }),
97        })
98        break
99
100      default:
101        return new Response(JSON.stringify({ error: 'Unknown action' }), {
102          status: 400, headers: { ...corsHeaders, 'Content-Type': 'application/json' },
103        })
104    }
105
106    const data = await resp.json()
107    return new Response(JSON.stringify(data), {
108      status: resp.ok ? 200 : resp.status,
109      headers: { ...corsHeaders, 'Content-Type': 'application/json' },
110    })
111  } catch (error) {
112    return new Response(JSON.stringify({ error: error.message }), {
113      status: 500, headers: { ...corsHeaders, 'Content-Type': 'application/json' },
114    })
115  }
116})

With the Edge Function deployed, use Lovable's chat to build the sales dashboard that highlights Freddy AI lead scoring. The key differentiator from standard CRM dashboards is the visual prioritization driven by Freddy scores. For the lead prioritization view, invoke list_contacts with the include parameters for freddy_score and last_activity_date. Sort by freddy_score descending so the highest-scoring leads appear at the top. Apply color coding: scores 75-100 (green/hot), 50-74 (yellow/warm), 25-49 (orange/cool), 0-24 (gray/cold). Include the days since last activity to help reps identify engaged leads with recent interaction. For deal pipeline health, invoke list_deals with the freddy_forecast_score included. Deals with low forecast scores despite being in late pipeline stages indicate high churn risk — surface these as an 'At Risk' section in your dashboard. For the contact creation flow (adding leads from your app), call create_contact from form submit handlers. Map your app's plan tiers to Freshsales tags ('free', 'trial', 'pro') for segment-based sales outreach. Use the fire-and-forget pattern (no await) so contact creation latency does not affect the user's registration experience. For connecting Freshsales with your existing Freshdesk support integration to show support ticket history alongside CRM data in a unified customer 360 view, RapidDev's team can help design the cross-Freshworks API architecture.