AgileCRM
AgileCRM is an all-in-one CRM platform that combines sales, marketing, and customer service tools in a single place. It helps small and mid-sized businesses manage contacts, track deals, run email campaigns, and handle support tickets without switching between apps.
Connecting AgileCRM to Coupler.io lets you pull your CRM data into spreadsheets, dashboards, or data warehouses automatically — no manual exports needed.
Why connect AgileCRM to Coupler.io?
Automate reporting — schedule regular data syncs so your reports are always up to date
Centralize your data — combine AgileCRM data with other sources like ad platforms or billing tools
Build custom dashboards — send data to Google Sheets, Looker Studio, Power BI, or BigQuery
Track pipeline health — monitor deals, tasks, and milestones without logging into AgileCRM
Prerequisites
Before you connect, make sure you have:
An active AgileCRM account
Your AgileCRM domain (the subdomain in your AgileCRM URL, e.g.,
yourcompanyfromyourcompany.agilecrm.com)Your AgileCRM email address (the one you use to log in)
Your AgileCRM REST API key (found in your AgileCRM account under Admin Settings → API & Analytics)
Quick start
Create a new data flow in Coupler.io and select AgileCRM as your data source.
Enter your AgileCRM credentials. Provide your AgileCRM domain (just the subdomain, not the full URL), your login email address, and your REST API key.
Choose an entity to import. Select which type of data you want to pull — for example, Contacts, Deals, or Tickets. See the table below for all available entities.
Configure your destination. Choose where you want your data to land — Google Sheets, Excel, BigQuery, or another supported destination — and map the fields as needed.
Run your data flow. Click Run to do a manual test first. Once everything looks right, set a refresh schedule so your data stays current automatically.
AgileCRM data overview
AgileCRM gives you access to a wide range of CRM data across sales, marketing, and support. When you connect through Coupler.io, you can pull structured data from any of the available entities and use it in your reports and dashboards.
Available entities
Contacts
Contact records with properties, tags, lead score, owner, and activity history
Companies
Company profiles with industry, size, website, and linked contacts
Deals
Deal name, value, stage, probability, close date, and assigned owner
Notes
Note content, associated record (contact/company/deal), author, and timestamp
Tasks
Task subject, type, due date, status, priority, and assignee
Events
Event title, start/end time, associated contact, and attendees
Milestones
Pipeline stage names, order, and probability percentages
Campaigns
Campaign name, status, type, stats, and creation date
Documents
Document name, type, associated contact or deal, and upload date
Ticket filters
Filter name, conditions, and associated ticket view settings
Tickets
Ticket subject, status, priority, assignee, requester, and timestamps
Contacts
Key fields
id
Unique contact identifier
first_name / last_name
Contact's full name
Primary email address
phone
Phone number
lead_score
Numeric lead score assigned in AgileCRM
tags
List of tags applied to the contact
owner
Team member responsible for the contact
created_time
Timestamp when the contact was created
updated_time
Timestamp of the last update
Companies
Key fields
id
Unique company identifier
name
Company name
url
Company website
industry
Industry category
no_of_employees
Estimated employee count
tags
Tags applied to the company
created_time
Record creation timestamp
Deals
Key fields
id
Unique deal identifier
name
Deal name
expected_value
Monetary value of the deal
probability
Percentage likelihood of closing
milestone
Current pipeline stage
close_date
Expected close date
owner
Assigned sales rep
contacts
Linked contact records
created_time
Deal creation timestamp
Tasks
Key fields
id
Unique task identifier
subject
Task title or description
type
Task type (call, email, follow-up, etc.)
due
Due date and time
status
Open or completed
priority
Low, normal, or high
owner
Assigned team member
Tickets
Key fields
id
Unique ticket identifier
subject
Ticket title
status
Open, closed, resolved, etc.
priority
Urgency level
group
Support group assigned
assignee
Agent handling the ticket
requester_email
Email of the person who raised the ticket
created_time
Ticket creation timestamp
updated_time
Last update timestamp
Common field combinations
Here are some useful ways to combine fields across entities:
Deal pipeline report — Deals
name+milestone+expected_value+close_date+ownerContact engagement report — Contacts
email+lead_score+tags+updated_timeSupport workload report — Tickets
assignee+status+priority+created_timeCampaign performance overview — Campaigns
name+status+type+created_timeTask completion tracking — Tasks
subject+type+due+status+owner
Use cases by role
Track open deals by stage and owner to spot pipeline gaps
Monitor lead scores to prioritize outreach
Report on deal close rates and average deal values over time
Use milestones data to analyze how deals progress through the pipeline
Pull campaign data into dashboards to compare performance across campaigns
Analyze contact tags and lead scores to segment audiences
Track new contact creation over time to measure inbound growth
Cross-reference campaign data with deal creation to measure campaign-to-revenue attribution
Monitor open ticket volume, priority distribution, and resolution time
Track tickets by assignee to balance team workload
Use ticket filter data to replicate saved views in external reporting tools
Identify trends in ticket creation to anticipate support demand
Platform-specific notes
AgileCRM uses Unix timestamps for
created_timeandupdated_timefields — you may need to convert these in your destination toolCustom fields defined in your AgileCRM account will appear in the data but field names may vary depending on your configuration
The Milestones entity returns pipeline stage definitions, not individual deal stages — use the
milestonefield in Deals for per-deal stage dataTicket filters returns saved filter configurations, not the tickets themselves — use the Tickets entity to get actual ticket records
Lead score values are cumulative and reflect all scoring activity up to the time of the sync
AgileCRM common issues
Connection issues
Missing data
Permission errors
Data discrepancies
Rate limits
AgileCRM FAQ
Last updated
Was this helpful?
