Agile CRM Integration

How LeadSync Creates Contacts in Agile CRM

Agile CRM's REST API lives at https://{your-domain}.agilecrm.com/dev/api/. LeadSync authenticates with HTTP Basic auth using the three-value credential pair you paste into the connection settings: Domain (your Agile subdomain), Email (your account login email), and REST API Key (Admin Settings › API & Analytics › REST API). Each new lead becomes a POST to /contacts with a structured properties array.

The contact create payload uses Agile CRM's {name, value, type} shape on every property -- type: SYSTEM for built-in fields like email, first_name, last_name, phone, company; type: CUSTOM for any custom field you have defined on your Agile CRM account. LeadSync inserts the correct type marker automatically based on the mapping you choose, so the contact lands fully populated in the right slots rather than dumped into notes.

Automatic "Facebook" Tag for Source Tracking

Every contact LeadSync creates in Agile CRM is tagged "Facebook" automatically -- the tag is added to the tags array on the contact create payload regardless of which Agile CRM view or campaign the contact lands in. This gives you a one-click filter in Agile CRM (Contacts › Filter by tag › Facebook) showing every paid-social lead with no extra configuration.

The tag also drives Agile CRM Campaigns (workflow automation): a Campaign with a "tag added" trigger fires the moment LeadSync writes a new lead, so welcome emails, task assignment, deal creation, and lead scoring rules all run automatically. If you run multiple ad sources through the same Agile CRM account, you can extend the tag list manually in your Campaign rules -- the "Facebook" tag is the durable signal LeadSync controls.

System Fields, Custom Fields, and Full-Name Splitting

The mapping screen lists every Agile CRM SYSTEM property -- first_name, last_name, company, title, phone, website, address, image -- alongside every CUSTOM field you have defined. LeadSync calls GET /custom-fields to pull the live list, so the moment you add a new custom field in Agile CRM it appears in the LeadSync dropdown.

When the lead arrives with a single full_name (the Facebook lead-ad default), LeadSync runs Utils::parseFullName to split it into first_name + last_name before constructing the properties array. That stops the entire name from collapsing into one field and means Agile CRM email merge tags like {{contact.first_name}} render correctly in your campaign emails.

Frequently Asked Questions

Domain, login email, and REST API Key. Domain is your Agile subdomain (the part before .agilecrm.com on your account URL). Email is the address you log in with. REST API Key comes from Admin Settings > API & Analytics > REST API. LeadSync stores all three encrypted and uses them as the HTTP Basic auth pair on every API call.

Yes. The tag "Facebook" is hard-coded into the LeadSync contact create payload, so every new contact lands tagged regardless of mapping choices. This gives you a clean Agile CRM filter and a reliable trigger for Agile Campaigns. If you also run LinkedIn or Google leads through Agile CRM, the source-specific tag still says "Facebook" today -- get in touch if you need source-aware tagging.

Yes. Build a Campaign with a "Tag added" trigger pointing at the Facebook tag, or a "Contact added" trigger if you want it to run for every new contact. Either way, every new paid-social lead enters the Campaign within seconds and welcome emails, task creation, or deal creation rules run automatically.

Yes. LeadSync calls Agile CRM's /custom-fields endpoint to enumerate every custom field you have defined, and they appear in the mapping dropdown alongside the standard SYSTEM properties. Map a lead form question to a custom field once and the value populates on every new lead through that connection.

first_name, last_name, email (added automatically), phone, company, title, website, address, and image. These are Agile CRM's built-in contact properties and they each appear in the LeadSync mapping dropdown so you can route specific lead form questions to the right slot.

When the lead arrives with only a full_name field (the Facebook default), LeadSync runs Utils::parseFullName to split it into first_name + last_name before sending. "Mary Jane Smith" arrives as first_name "Mary" and last_name "Jane Smith". This makes Agile email merge tags like {{contact.first_name}} render correctly in your campaign emails.

Agile CRM de-duplicates contacts by email by default. A repeat submission updates the existing contact's properties and adds the Facebook tag if it is not already present, rather than creating a new contact. Your contact count and reporting stay accurate.

Yes. Each LeadSync connection is one ad source pointing at one Agile CRM account, so create separate connections for Facebook and LinkedIn. Both will write into the same Agile CRM contacts table and you can use Agile Campaign rules to route or score them differently based on the lead form name or other mapped fields.

Yes. LeadSync supports Agile CRM as a destination for lead forms from Facebook Lead Ads, Instagram Lead Ads, Google Ads lead form extensions, LinkedIn Lead Gen Forms, and TikTok Lead Generation. Each source is its own LeadSync connection but all use the same Agile CRM helper.

Available Integrations

How It Works

How LeadSync Creates Contacts in Agile CRM

Automatic "Facebook" Tag for Source Tracking

System Fields, Custom Fields, and Full-Name Splitting

Frequently Asked Questions

Start Syncing Leads to Agile CRM