Integration
Fergus Integration
Connect your CRM pipeline to Fergus. Automatically create jobs, sync calendars, forward messages, and keep both systems in sync without manual data entry.
On this page
- What does it do?
- What’s new in September 2026
- Getting started
- The tabbed layout
- How it works, step by step
- Create Work
- Stage actions
- Existing opportunities
- Fergus → CRM job sync
- Custom fields (CRM → Fergus)
- Stay Updated
- Job lifecycle
- Always sync
- Contact tags
- Custom fields (Fergus → CRM)
- Messages
- Message sync
- Calendar
- Calendar sync
- Activity
- Activity log
- Your data and privacy
- Common questions
What does it do?
Your CRM is where you manage your opportunities and sales pipeline. Fergus is where you run your jobs.Fergus Integration connects the two, so when an opportunity is ready to become a job, it happens automatically. And it doesn't stop there: calendars stay in sync, files are forwarded, and lifecycle changes in Fergus flow back into your pipeline in real time.
Saves time
No more manually re-entering customer details, forwarding messages, or updating pipeline stages.
No duplicates
If a job already exists for that opportunity, it won't be created again - even if the opportunity moves through multiple stages.
Two-way sync
Pipeline stages, calendars, messages, and job status all flow between your CRM and Fergus automatically.
What's new in September 2026New
This release adds four major new capabilities to the integration.
Calendar sync
Fergus calendar events automatically appear in your CRM calendars, and CRM appointments can create events in Fergus. Matched users get events on their personal calendars.
Message sync
Inbound emails, SMS, and WhatsApp messages are automatically saved as notes on the matching Fergus job — with any attachments copied across as files.
Always sync
Contact details, notes, and job values stay in sync automatically between Fergus and your CRM — no manual updates needed. Changes in either system flow to the other.
Custom field mapping
Map CRM fields to Fergus fields and vice versa. Data flows in both directions — from CRM to Fergus at job creation, and from Fergus back to CRM when lifecycle events fire.
Getting started
Setup takes about two minutes and only needs to be done once. The new features (calendar sync, message sync) each have their own enable toggle. They're off by default and you turn on only what you need.
- 1
Install the app from the CRM Marketplace
Search for 'Fergus Integration' and click Install.
- 2
Connect your Fergus account
Sign in with your Fergus credentials. Your account is connected securely.
- 3
Set up stage actions (Create Work tab)
Choose which stages create Enquiries, Quotes, Estimates, or Charge-Ups. Optionally enable Sync Jobs created in Fergus to CRM.
- 4
Configure lifecycle sync (Stay Updated tab)
Set up how Fergus job progress flows back to your CRM pipeline. Enable always-sync to keep contact details, notes, and values in sync automatically.
- 5
Enable message sync (Messages tab)
Toggle on automatic message sync so inbound emails, SMS, and WhatsApp messages are saved as notes on the matching Fergus job.
- 6
Set up calendar sync (Calendar tab)
Choose sync direction (Fergus → CRM, CRM → Fergus, or both). Map your Fergus users to CRM users so events appear on the right calendars.
The tabbed layoutNew
Settings are organised into five tabs, each focused on a different part of the integration. When you first open a tab, a brief hint explains what it's for. You can dismiss it once you're familiar.
Choose which CRM stages create enquiries, quotes, estimates, or charge-ups in Fergus. Also configure Sync Jobs created in Fergus to CRM.
How Fergus job progress flows back to your CRM pipeline. Job lifecycle stage moves, and always-sync for contact details, notes, and values.
Enable or disable automatic message sync — inbound emails, SMS, and WhatsApp messages are saved as notes on the matching Fergus job, with attachments copied as files.
Sync direction, user mapping, and calendar configuration.
A log of jobs and opportunities created by the integration. Check here to confirm things are working or troubleshoot an issue.
How it works, step by step
The opportunity moves stage
Fergus Integration is notified automatically. The job is usually created within a minute.
Customer lookup
The contact details are matched against Fergus customers by email, then phone, then name. If no match, a new customer is created.
Job address
The address from the CRM contact is used. If the customer already has a matching address in Fergus, it's reused.
Job created
The job is created in Fergus using the opportunity name and the configured job type.
CRM updated
The opportunity name is prefixed with the Fergus job number (e.g. [FERG-1701]), a contact note with a Fergus link is added, and lifecycle tags are applied to the contact.
Create Fergus enquiries and jobs from CRM stage changes
For each stage in your pipeline, you choose one of five options. Stages set to Do nothing are completely ignored.
Do nothing
Opportunities that move into this stage are ignored. This is the default.
Create an Enquiry
A lightweight pre-sale lead is created in the Fergus inbox. When converted to a Job, tracking starts automatically.
Create a Quote
A Quote job is created. The integration watches for acceptance or rejection.
Create an Estimate
An Estimate job is created. Same lifecycle tracking as Quotes.
Create a Charge-Up
A Charge-Up job is created for pre-approved work billed on time and materials.
What about existing opportunities?
When you first configure a stage, any opportunities already sitting there are shown for review. You choose: create a new Fergus job, link to an existing one, or skip. Nothing is created automatically.
Sync jobs created in Fergus to CRM
Jobs created directly in Fergus (phone calls, walk-ins, the Fergus app) automatically get a CRM opportunity, so your sales pipeline is always complete.
When a job is created directly in Fergus, automatically create an opportunity in your CRM pipeline.
How it works
Every minute, the integration checks Fergus for new jobs. If a job doesn’t have a matching CRM opportunity, one is created in the pipeline and stage you’ve configured.
Contact matching
The Fergus customer is matched to a CRM contact by email first, then phone. If no match exists, a new CRM contact is created.
No backfill
Only jobs created after you enable this feature are synced. Existing jobs are not retroactively imported.
Full lifecycle tracking
Once the opportunity is created, it’s tracked just like any other — quote outcomes, phase events, and lifecycle changes all flow back automatically.
Custom field mapping: CRM → FergusNew
When a job is created from an opportunity, custom field values from the CRM contact and opportunity can be written to the Fergus job. For example, map a "Property Type" custom field in CRM to the job description in Fergus.
Where to find it
Look for the small mappings icon next to each configured stage action on the Create Work tab and next to each lifecycle event on the Stay Updated tab. Hovering over it shows the standard field mappings for that action. Clicking it opens the field mapping modal.
Click the mappings icon next to any configured stage to open the field mapping modal
The field mapping modal
Clicking the mappings icon opens a modal with two sections:
Field Mappings
Map CRM fields to Fergus fields
Custom field mappings
Add your own mappings between CRM and Fergus fields. Choose a CRM field (standard or custom) and a Fergus field from the dropdowns, then click Save. The integration auto-suggests matches based on field names — you can accept, dismiss, or ignore them.
Standard mappings (read-only)
Below the custom mappings, you’ll see the built-in mappings that always run (e.g. Contact Name → Customer Name). These can’t be changed but are shown for reference.
Tips
Per-pipeline configuration
Each pipeline can have its own set of field mappings. Different pipelines can map different fields.
Ordering and concatenation
Mappings are applied in order. If multiple mappings target the same Fergus or CRM field, their values are concatenated (separated by line breaks). Use the arrow buttons to reorder.
File fields
File upload fields in CRM can be mapped to Fergus file fields (Job Files, Customer Files, or Enquiry Files). The integration copies the file content across.
Update CRM opportunities as Fergus jobs progress
Fergus Integration can automatically move the opportunity to a different stage, and optionally set its status to Won, Lost, or Abandoned, based on what happens in Fergus.
Each event can independently set the opportunity stage and/or status (Won, Lost, Abandoned).
Quote/estimate published
Finalised and ready to send.
Quote/estimate sent
Sent to the customer.
Quote/estimate accepted
Job moves to active status.
Quote/estimate rejected
Marked as rejected in Fergus.
Enquiry contacted
The enquiry status changed to "Contacted" in Fergus.
Enquiry rejected
The enquiry was rejected in Fergus.
Enquiry converted to job
A Fergus user converted the Enquiry into a Job.
Job completed
Job reaches "Completed" status. Opportunity value updated to finalised invoice total.
Scheduled
Any phase of the job is booked into the Fergus schedule.
Work completed
All phases marked as work-complete.
Invoiced
All phases invoiced.
Placed on hold
Job placed on hold. Automatically restores when taken off hold.
Archived
Job archived. Automatically restores when un-archived.
Keep contact details, notes, and job values in syncNew
Once a Fergus customer is linked to a CRM contact, their details stay in sync automatically. No manual updates needed. This runs continuously, independent of pipeline actions.
Contact details
Name, email, phone, address, and company name stay in sync between Fergus customers and CRM contacts. Changes in either system are reflected in the other.
Customer discovery
Fergus customers that aren't yet linked to a CRM contact are automatically discovered by matching email or phone number. When a match is found, the contact is linked and kept in sync going forward.
Notes
Notes created or edited on Fergus jobs and customers sync to the matching CRM contact, and vice versa. Only notes created after sync is enabled are included.
Job values
Quote and invoice totals from Fergus are written to the CRM opportunity value. The value updates as quotes are accepted and invoices are finalised. If you manually edit the opportunity value in the CRM, the lock is respected until the next authoritative Fergus event (e.g. accepted quote or invoice).
Custom field mapping: Fergus → CRMNew
When a lifecycle event fires (quote accepted, invoiced, etc.), Fergus job data can be written back to the CRM opportunity's custom fields. For example, write the Fergus job total or completion date to a CRM field.
Where to find it
Look for the small mappings icon next to each configured stage action on the Create Work tab and next to each lifecycle event on the Stay Updated tab. Hovering over it shows the standard field mappings for that action. Clicking it opens the field mapping modal.
Click the mappings icon next to any configured stage to open the field mapping modal
The field mapping modal
Clicking the mappings icon opens a modal with two sections:
Field Mappings
Map CRM fields to Fergus fields
Custom field mappings
Add your own mappings between CRM and Fergus fields. Choose a CRM field (standard or custom) and a Fergus field from the dropdowns, then click Save. The integration auto-suggests matches based on field names — you can accept, dismiss, or ignore them.
Standard mappings (read-only)
Below the custom mappings, you’ll see the built-in mappings that always run (e.g. Contact Name → Customer Name). These can’t be changed but are shown for reference.
Tips
Per-pipeline configuration
Each pipeline can have its own set of field mappings. Different pipelines can map different fields.
Ordering and concatenation
Mappings are applied in order. If multiple mappings target the same Fergus or CRM field, their values are concatenated (separated by line breaks). Use the arrow buttons to reorder.
File fields
File upload fields in CRM can be mapped to Fergus file fields (Job Files, Customer Files, or Enquiry Files). The integration copies the file content across.
Save CRM messages and files to Fergus jobsNew
Inbound emails, SMS, and WhatsApp messages are automatically saved as notes on the matching Fergus job, so your team has full context in one place. Any attachments are copied across as files too.
When a customer sends an email or WhatsApp message, it's automatically saved as a note on the matching Fergus job.
How it works
When an inbound message arrives in your CRM (email, SMS, or WhatsApp), the integration matches the sender to a Fergus job via the tracked opportunity, then saves the message as a note on the job. Any attachments are uploaded as files.
What gets synced
The message subject and body are saved as a Fergus job note. All attachment types are supported, including photos, PDFs, documents, and spreadsheets, and are uploaded with their original filenames.
When it doesn’t sync
Messages from contacts not linked to an active Fergus job are flagged for review. If a contact has multiple active jobs, you choose which one in the review queue. Duplicate messages (same ID) are only processed once.
Keep Fergus and CRM calendars in syncNew
Keep your Fergus calendar and CRM calendars in sync. Scheduled jobs, site visits, and other calendar events automatically appear in both systems.
Fergus calendar events appear in your CRM calendars
CRM appointments create events in Fergus
Fergus → CRM (outbound)
Fergus calendar events are synced to your CRM calendars every minute. Matched users get events as appointments on their personal CRM booking calendars — these show up on the user's calendar and can block time for scheduling. Unmatched users' events appear as block slots on a shared event calendar.
CRM → Fergus (inbound)
When an appointment is created in your CRM on a mapped user's calendar, a corresponding event is created in Fergus. Cancelled appointments are removed from the Fergus calendar. When inbound sync is first enabled, existing CRM appointments from the past 30 days are backfilled into Fergus.
User mapping
Fergus users are automatically matched to CRM users by email. Where auto-match fails, you can manually assign the correct CRM user. Each user can be individually enabled or disabled for calendar sync.
Job-linked appointments
When a calendar event is linked to a Fergus job, the CRM appointment is connected to the real customer contact. It shows up on their timeline and includes the job address.
Conflict resolution
If an event is edited in both systems, the most recent change wins. After write-back, both sides are refreshed to prevent ping-pong.
Reconciliation
A background reconciliation check runs every 5 minutes to catch events that were deleted or changed outside the normal sync window. Orphaned CRM events are cleaned up automatically.
Track jobs and opportunities
The Activity tab shows a log of jobs and opportunities created by the integration: enquiries created, stages moved, quote outcomes, and any problems it ran into.
Job created / Enquiry created
Shows the opportunity name, Fergus job number, and a link to open the job in Fergus.
Enquiry contacted / rejected / converted
Shows enquiry lifecycle transitions detected in Fergus.
Quote lifecycle (published, sent, accepted, rejected)
Shows the outcome and which stage/status the opportunity was moved to.
Phase events (scheduled, completed, invoiced)
Shows job milestone transitions.
Hold / Archive / Un-archive
Shows hold and archive transitions with automatic stage restoration.
Opportunity deleted
Shows when a CRM opportunity was deleted. The Fergus job is unaffected; only syncing stops.
Failed
Shows errors with details for troubleshooting.
Your data and privacy
Fergus Integration is operated by FernNola. Here's a plain-English summary of what data is stored and why.
Connection tokens
Secure tokens (not passwords) are stored encrypted and cleared on uninstall.
Activity log data
Contact names, opportunity names, Fergus job numbers, pipeline/stage names, and error details.
Calendar sync data
Calendar event IDs, user mapping (email-based), and content hashes for change detection. No event content is stored beyond what's needed for sync.
Message sync data
Message IDs, contact names, attachment metadata, and processing status. Message content and file attachments are streamed directly to Fergus and not stored by FernNola.
Contact and customer data
Contact details are read from CRM and written to Fergus during job creation. Not stored beyond the activity log.
Common questions
What if an opportunity moves back into a stage after a job already exists?
Nothing happens. Once a Fergus job exists for an opportunity, it will never be created again.
Can I use this with multiple pipelines?
Yes. Each pipeline has its own stage actions, lifecycle config, and custom field mappings.
Do I need to enable all the new features?
No. Calendar sync and message sync each have their own toggle. Enable only what you need — they're both off by default.
Will calendar sync create duplicate events?
No. Each event is tracked with a unique ID. If it already exists, it's updated rather than duplicated. Events created by the sync are marked so they're never re-synced in the other direction.
What happens if I delete a CRM opportunity?
The integration stops syncing to that opportunity. The Fergus job is completely unaffected — it remains real and active.
Can I set an opportunity to Won when a quote is accepted?
Yes. In the Job Lifecycle config, each event has a "Set status" dropdown. You can independently choose the stage move and the status change.
How does the contact tag lifecycle work?
Tags are mutually exclusive — only the latest lifecycle tag is shown. As the job progresses (Quote Sent → Accepted → Scheduled → Completed → Invoiced), the old tag is removed and the new one is added.
What if a Fergus user doesn't have a CRM account?
Their calendar events still sync — they appear as block slots on a shared calendar rather than appointments on a personal calendar. You can change this behaviour in the Calendar tab.
How quickly do changes sync?
Pipeline events: within a minute. Calendar sync: every few minutes. Message sync: within a minute of the message arriving.
What happens if I uninstall?
Syncing stops immediately. Jobs, calendar events, and notes already created are unaffected. Connection tokens are cleared on uninstall.
Fergus Integration by FernNola - built for trade businesses on Fergus