Resources · Make integration

SugarCRM Make integrationAutomate SugarCRM with Make.

Your CRM records can move on their own the moment someone saves them. The SugarCRM Make integration gives you 137 modules, including 23 instant triggers, for sales and support teams. This guide connects your account and walks you through a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SugarCRM Make integration do?

The SugarCRM Make integration links your SugarCRM account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates, reads, updates or deletes a record. When a lead, a case or an opportunity changes in SugarCRM, Make can react and carry the data to the next step for you.

Every new lead gets a follow-up task. Watch Leads fires as soon as a lead is created or edited, and Create a Call attaches a follow-up call to that lead. Nobody has to remember to log the next step.

Support cases never sit unread. Watch Cases passes each new or edited case to Make, which can look up the related account with Get an Account and add the context with Create a Note before the team opens it.

A deal that moves feeds the rest of your tools. Watch Opportunities hands the deal over each time it changes. When the change is a signature, Create a Contract records the agreement without anyone retyping it.

All 23 triggers of this app are instant, and 91 actions plus 23 searches cover the rest. When a listed module falls short, Make an API Call reaches any endpoint of the SugarCRM API with the same connection. Make's own documentation for this app carries a warning that it is AI-generated, so check important details against SugarCRM. If you want to learn the editor properly, the Make training starts from zero, Make pricing explains how operations are counted, and the n8n vs Make comparison helps if you are still choosing a tool.

Connect

How do you connect SugarCRM to Make?

  1. 01

    Create an OAuth key in SugarCRM

    In SugarCRM, open the Admin panel, go to the System section and click OAuth Keys. From the three-dots menu, choose Create OAuth Key. If SugarCRM asks for a callback URI, paste https://www.integromat.com/oauth/cb/sugarcrm11.

  2. 02

    Copy the two credentials

    SugarCRM then shows a Client ID and a Client secret. Copy both somewhere safe for a moment. Make's documentation also lists an active SugarCRM account with a valid username and password as a prerequisite.

  3. 03

    Create the connection in Make

    Add any SugarCRM module to your scenario and click Create a connection. A connection is your SugarCRM account linked to Make once, then reused by every SugarCRM module. Give it a Connection name if you like, paste the credentials and confirm.

First scenario

Your first scenario: log a call for every new lead

GoalWhen a lead is created or updated in SugarCRM, Make creates a follow-up call linked to it.

  1. 01

    Start a blank scenario

    Open the Scenarios page in Make, create a new scenario and click the big + in the middle of the editor. This is where the first module goes, the one that starts everything.

  2. 02

    Add Watch Leads

    Search for SugarCRM, pick Watch Leads, click Create a webhook and then Create a connection with the OAuth credentials you copied. Make now waits for SugarCRM to call it.

  3. 03

    Add Create a Call

    Click the + on the right of Watch Leads and choose Create a Call. Map data from the lead in the first module into the call, so each bundle (one lead passing through) produces one call.

  4. 04

    Test with Run once

    Click Run once, then create or edit a test lead in SugarCRM. Make runs the scenario one time and shows the bundle each module received, so you can check the call before going live.

  5. 05

    Switch the scenario on

    Turn the scenario on. Because Watch Leads is an instant trigger, it has no clock to set: SugarCRM calls Make through the webhook each time a lead is saved, and the call appears right after.

Triggers

What starts a SugarCRM scenario

23 modules start a scenario when something happens in SugarCRM. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by SugarCRM as soon as it happens.

SugarCRM1Watch Accounts

Watch Accounts

Instant trigger

In MakeTriggers when a new account has been created or an existing one has been updated.

This trigger starts your scenario whenever a company account appears in SugarCRM or someone edits one, and hands its details to the next module.

How it fires
instant. SugarCRM calls Make through a webhook as soon as the account is saved.
When to use it
pick it when a new customer company should also exist in your billing or project tool without anyone retyping it.
Watch out
in SugarCRM an account is the company, not the person. For people, pick Watch Contacts, a separate trigger further down the list.
SugarCRM2Watch Bugs

Watch Bugs

Instant trigger

In MakeTriggers when a new bug has been created or an existing one has been updated.

Each bug logged in SugarCRM, and each later change to it, reaches Make as a fresh bundle you can route to the people who fix things.

How it fires
instant, through a webhook SugarCRM calls the moment the bug is created or edited.
When to use it
your support team records product defects in SugarCRM while developers live in another tool, and you want the two to stay in step.
Watch out
an edit fires the trigger again, so a bug touched several times sends several bundles. Design the next module to update, not duplicate.
SugarCRM3Watch Calls

Watch Calls

Instant trigger

In MakeTriggers when a new call has been created or an existing one has been updated.

Watch Calls gives Make every call a rep schedules or logs in SugarCRM, which turns phone activity into data other tools can use.

How it fires
instant. SugarCRM pings Make by webhook when a call record is created or changed.
When to use it
a manager wants each logged call copied into a shared activity sheet, or a reminder sent to the contact before the call happens.
Watch out
rescheduling a call counts as an update and fires again, which is handy for reminders but can repeat a message if you do not plan for it.
SugarCRM4Watch Campaigns

Watch Campaigns

Instant trigger

In MakeTriggers when a new сampaign has been created or an existing one has been updated.

When marketing sets up a campaign in SugarCRM or adjusts one, this trigger passes it to Make so the rest of your stack hears about it.

How it fires
instant, via a webhook that SugarCRM calls right after the campaign is saved.
When to use it
you announce every launched campaign in the team chat, or mirror its name and dates in the tool that plans your content.
Watch out
both creation and edits wake the scenario. If only launches matter to you, check the data from the bundle before acting on it.
SugarCRM5Watch Cases

Watch Cases

Instant trigger

In MakeTriggers when a new case has been created or an existing one has been updated.

Every support case opened in SugarCRM, and every change made to it afterwards, lands in Make so you can react while the customer is still waiting.

How it fires
instant. SugarCRM notifies Make through a webhook the moment the case is saved.
When to use it
alert the on-duty agent when a case arrives, or add account context to the case with a lookup and a note.
Watch out
status changes and comments count as updates, so a busy case can trigger many runs, and each run spends operations on your plan.
SugarCRM6Watch Categories

Watch Categories

Instant trigger

In MakeTriggers when a new category has been created or an existing one has been updated.

Categories organize products in SugarCRM, and this trigger tells Make when one is added or renamed so every tool shares the same catalog structure.

How it fires
instant, through a webhook SugarCRM calls when a category record is created or edited.
When to use it
your online store or quoting tool needs the same product categories as the CRM, and you are tired of keeping two lists by hand.
Watch out
categories rarely change, so this scenario stays quiet most of the time. Test it with Run once on a dummy category first.
SugarCRM7Watch Contacts

Watch Contacts

Instant trigger

In MakeTriggers when a new contact has been created or an existing one has been updated.

Watch Contacts sends Make each person added to SugarCRM, plus every edit to their details, ready to be synced wherever that person also needs to exist.

How it fires
instant. The webhook fires as soon as SugarCRM saves the contact.
When to use it
add new contacts to your newsletter tool, or keep a phone number fixed in SugarCRM identical in the helpdesk.
Watch out
Watch Accounts and Watch Contacts sit close together in the list. The first follows companies, this one follows people, so check the name before you click.
SugarCRM8Watch Contracts

Watch Contracts

Instant trigger

In MakeTriggers when a new contract has been created or an existing one has been updated.

This trigger follows the contracts stored in SugarCRM and wakes Make each time one is drafted or modified, so paperwork stops hiding in a single tab.

How it fires
instant, via the webhook SugarCRM calls when the contract record is saved.
When to use it
legal or finance want a heads-up when a contract appears, or its details copied into the tool that tracks renewals.
Watch out
a contract edited by several people sends a bundle per save. Route updates to an Update module downstream rather than creating new rows each time.
SugarCRM9Watch Currencies

Watch Currencies

Instant trigger

In MakeTriggers when a new currency has been created or an existing one has been updated.

Watch Currencies reports to Make whenever an admin adds a currency to SugarCRM or changes one, so other tools can stay aligned.

How it fires
instant. SugarCRM calls Make through a webhook once the currency record is saved.
When to use it
finance keeps a reference sheet of the currencies sales can quote in, and wants it updated without a reminder email.
Watch out
this is admin data. Few people touch it, so a scenario built on it runs rarely, and a mistake there can spread to every tool you sync.
SugarCRM10Watch Custom Queries

Watch Custom Queries

Instant trigger

In MakeTriggers when a new custom query has been created or an existing one has been updated.

This trigger tells Make each time a custom query record is created or rewritten in SugarCRM, so admin changes stop going unnoticed.

How it fires
instant, through a webhook called as soon as the query is saved in SugarCRM.
When to use it
you keep a log of who changed which report definition, useful when several admins share the CRM and numbers start to disagree.
Watch out
it watches the query records themselves, not the results they return. To act on matching records, use the Search modules instead.
SugarCRM11Watch Email Templates

Watch Email Templates

Instant trigger

In MakeTriggers when a new email template has been created or an existing one has been updated.

Whenever someone writes a new email template in SugarCRM or rewords an existing one, Make receives it and can share or archive the new version.

How it fires
instant. SugarCRM pings Make by webhook right after the template is saved.
When to use it
a marketing lead wants to review every template change, or keep a copy of each version in a shared document.
Watch out
small typo fixes also count as updates. Expect a bundle for each save, not one per finished template.
SugarCRM12Watch Forecast Worksheets

Watch Forecast Worksheets

Instant trigger

In MakeTriggers when a new forecast worksheet has been created or an existing one has been updated.

Forecast worksheets hold what reps expect to close, and this trigger passes each new or edited worksheet to Make for reporting.

How it fires
instant, via a webhook SugarCRM calls whenever the worksheet is saved.
When to use it
a sales director wants forecast changes collected in one spreadsheet or posted to a leadership channel as they happen.
Watch out
reps adjust forecasts often, so the number of runs can climb fast. Keep an eye on the operations the scenario consumes.
SugarCRM13Watch Inbound Emails

Watch Inbound Emails

Instant trigger

In MakeTriggers when a new inbound email has been created or an existing one has been updated.

This trigger catches inbound email records in SugarCRM as they are created or updated and gives their data to your scenario.

How it fires
instant. SugarCRM calls Make through a webhook the moment the record is saved.
When to use it
your team wants a notification or an audit trail each time an inbound email setup is added or changed in the CRM.
Watch out
make's documentation says little about these records. Click Run once on a test change and read the bundle before mapping anything.
SugarCRM14Watch Leads

Watch Leads

Instant trigger

In MakeTriggers when a new lead has been created or an existing one has been updated.

Watch Leads is the trigger most sales teams start with: every fresh lead, and every edit to one, reaches Make straight away.

How it fires
instant. SugarCRM calls the webhook as soon as a lead is saved, with no clock to configure.
When to use it
assign a follow-up call, alert the owner in chat, or enrich the lead with data from another app while it is still warm.
Watch out
if your scenario updates the same lead afterwards, that update fires the trigger again. Avoid writing back to the lead you are watching.
SugarCRM15Watch Manufacturers

Watch Manufacturers

Instant trigger

In MakeTriggers when a new manufacturer has been created or an existing one has been updated.

Manufacturers in SugarCRM describe who makes the products you sell. This trigger reports each new or edited manufacturer to Make.

How it fires
instant, through a webhook SugarCRM calls after the manufacturer record is saved.
When to use it
your purchasing or inventory tool keeps its own supplier list and should follow the CRM whenever a brand is added.
Watch out
a renamed manufacturer arrives as an update, not a new record. Match on something stable before overwriting data elsewhere.
SugarCRM16Watch Meetings

Watch Meetings

Instant trigger

In MakeTriggers when a new meeting has been created or an existing one has been updated.

Every meeting booked in SugarCRM, and every change to its time or attendees, lands in Make where you can push it to calendars or reminders.

How it fires
instant. SugarCRM notifies Make via webhook when the meeting is saved.
When to use it
send the prospect a confirmation, create a prep document for the rep, or add the meeting to a shared team calendar.
Watch out
moving a meeting fires the trigger a second time. If you send confirmations, make sure the second message reads as a change, not a new booking.
SugarCRM17Watch Notes

Watch Notes

Instant trigger

In MakeTriggers when a new note has been created or an existing one has been updated.

Notes are where reps write down what a customer said. Watch Notes passes each new or edited note to Make so that context travels with the deal.

How it fires
instant, via a webhook SugarCRM calls right after the note is saved.
When to use it
copy notes about a key account into the channel where the whole account team talks, so nobody misses a promise made on a call.
Watch out
notes can contain personal or sensitive details. Think about who can read the destination before you pipe them out.
SugarCRM18Watch Opportunities

Watch Opportunities

Instant trigger

In MakeTriggers when a new opportunity has been created or an existing one has been updated.

This trigger follows your pipeline: each opportunity created or moved in SugarCRM reaches Make as a bundle ready for the next module.

How it fires
instant. The webhook fires as soon as SugarCRM saves the opportunity.
When to use it
celebrate won deals in chat, prepare an invoice draft, or create the project that starts once a deal closes.
Watch out
the trigger fires on every edit, not only when a deal is won. Read the bundle before launching anything that should happen once.
SugarCRM19Watch Products

Watch Products

Instant trigger

In MakeTriggers when a new product has been created or an existing one has been updated.

Watch Products keeps Make informed of your SugarCRM catalog: a product added, a price or description changed, and the scenario runs.

How it fires
instant, through a webhook SugarCRM calls when a product record is saved.
When to use it
your e-commerce site or quoting tool must show the same products as the CRM, and a sales rep should never quote an old price.
Watch out
a bulk edit of many products sends many bundles at once, and each one costs operations on your Make plan.
SugarCRM20Watch Product Types

Watch Product Types

Instant trigger

In MakeTriggers when a new product type has been created or an existing one has been updated.

Product types group your catalog into families. This trigger tells Make when a type is created in SugarCRM or its label changes.

How it fires
instant. SugarCRM calls Make by webhook as soon as the product type is saved.
When to use it
another tool filters or reports by the same families, and you want its list to follow the CRM without manual edits.
Watch out
product types and categories are separate records in SugarCRM, with separate triggers. Make sure you watch the one your team really uses.
SugarCRM21Watch Projects

Watch Projects

Instant trigger

In MakeTriggers when a new project has been created or an existing one has been updated.

When a project is opened in SugarCRM or its details shift, Watch Projects sends it to Make so the delivery team hears about it without asking.

How it fires
instant, through a webhook called right after SugarCRM saves the project.
When to use it
mirror each new project in the task manager your delivery team works in, with the same name and owner.
Watch out
updates fire too. If the scenario creates a task board, look it up first so an edited project does not get a second board.
SugarCRM22Watch Prospects

Watch Prospects

Instant trigger

In MakeTriggers when a new prospect has been created or an existing one has been updated.

Prospects are the cold names in SugarCRM, before they turn into leads. This trigger forwards each new or edited prospect to Make.

How it fires
instant. SugarCRM calls Make through a webhook when the prospect is saved.
When to use it
push freshly imported prospects into an outreach tool, or flag the ones missing an email address for cleanup.
Watch out
a large import creates many prospects in one go, and each becomes its own bundle, so check your plan before loading a big list.
SugarCRM23Watch Revenue Line Items

Watch Revenue Line Items

Instant trigger

In MakeTriggers when a new revenue line item has been created or an existing one has been updated.

Revenue line items break a deal down into what is actually sold. This trigger sends each new or changed line to Make as its own bundle.

How it fires
instant, via a webhook SugarCRM calls when the line item is saved.
When to use it
finance wants each sold product and amount copied into a revenue sheet or an invoicing tool, line by line.
Watch out
one opportunity can hold several lines, and editing the deal may touch all of them. Expect several bundles for one change.
Modules

What SugarCRM can do inside a scenario

SugarCRM gives you 114 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SugarCRM1

Create a Bug

Action

In MakeCreates a new bug.

Create a Bug files a new bug record in SugarCRM from data that arrives elsewhere, so a defect reported by a customer is logged without copy and paste.

When to use it
a form or a helpdesk ticket describes a product problem, and support wants it tracked in the CRM next to the customer.
Watch out
run it after a search when the same report can come in twice, or you will end up with duplicate bugs.
SugarCRM2

Create a Call

Action

In MakeCreates a new call.

This module schedules or logs a call in SugarCRM, giving a rep a clear next step tied to the right record.

When to use it
right after Watch Leads, so every new lead has a follow-up call on someone's list without a manager handing it out.
Watch out
map the lead from Watch Leads into the call, otherwise the call exists but is attached to nothing.
SugarCRM3

Create a Case

Action

In MakeCreates a new case.

Create a Case opens a support case in SugarCRM, so a request that comes in by email, chat or form joins the same queue as the rest.

When to use it
your contact form lives outside SugarCRM and support wants every complaint to become a case attached to the customer's account.
Watch out
find the account first with Search Accounts, so the case is linked to an existing company instead of floating on its own.
SugarCRM4

Create a Category

Action

In MakeCreates a new category.

With this module, Make adds a product category to SugarCRM, which keeps the CRM catalog organized the same way as your shop or ERP.

When to use it
a new range appears in the tool that owns your catalog, and sales should see it under the right heading in SugarCRM.
Watch out
categories are shared by the whole team. Check with Search Categories that the name does not already exist before you add it.
SugarCRM5

Create a Contact

Action

In MakeCreates a new contact.

Create a Contact adds a person to SugarCRM from any source Make can read, from a webinar sign-up to a signed quote.

When to use it
people who register for an event or buy online should appear in the CRM with their details, ready for the sales team.
Watch out
the module does not check for duplicates. Put Search Contacts in front of it and create only when nothing comes back.
SugarCRM6

Create a Contract

Action

In MakeCreates a new contract.

This action records a contract in SugarCRM, so the agreement sits next to the account and the deal it came from.

When to use it
a deal is marked won, or an e-signature tool reports a signed document, and the contract should exist in the CRM straight away.
Watch out
link the contract to the right account by mapping its identifier from an earlier module, not by typing a name.
SugarCRM7

Create a Currency

Action

In MakeCreates a new currency.

Create a Currency adds a new currency to your SugarCRM setup, which lets reps price deals for a market you just opened.

When to use it
a finance tool or reference sheet is the master list of currencies, and SugarCRM should follow it instead of being edited by hand.
Watch out
this changes admin settings that affect every user. Test on a sandbox account with Run once before switching it on.
SugarCRM8

Create a Custom Query

Action

In MakeCreates a new custom query.

This module saves a new custom query in SugarCRM, an admin record that most teams never need to touch.

When to use it
you roll out the same set of queries to several SugarCRM instances and want to create them from one definition kept elsewhere.
Watch out
it is an admin tool, rarely needed in everyday scenarios. If you only want to find records, the Search modules are simpler.
SugarCRM9

Create a Lead

Action

In MakeCreates a new lead.

Create a Lead turns an outside signal, a form entry, a chatbot answer or a scraped profile, into a lead that sales can work in SugarCRM.

When to use it
your landing pages or ad forms collect contacts outside the CRM, and each one should reach a rep within the same run.
Watch out
combine it with Search Leads, because the same person often fills in two forms and would otherwise become two leads.
SugarCRM10

Create a Manufacturer

Action

In MakeCreates a new manufacturer.

This action adds a manufacturer to SugarCRM, so products from a new brand can be attached to it from day one.

When to use it
purchasing signs a new supplier in its own tool, and the CRM catalog should know that brand before products start arriving.
Watch out
spell the name exactly as in your source system. A slightly different spelling creates a second manufacturer that is hard to spot later.
SugarCRM11

Create a Meeting

Action

In MakeCreates a new meeting.

Create a Meeting puts a meeting on the SugarCRM record it concerns, which keeps every appointment with a customer in one history.

When to use it
a prospect books a slot through your scheduling tool, and the meeting should show up in SugarCRM for the rep who owns the lead.
Watch out
map the date from the booking tool, and test with Run once to check the hour lands where you expect.
SugarCRM12

Create an Account

Action

In MakeCreates a new account.

This module creates a company account in SugarCRM, the record that contacts, deals and cases all hang from.

When to use it
a new customer signs up on your website or appears in your billing tool, and sales needs the company in the CRM to start working it.
Watch out
search first with Search Accounts. Two accounts for the same company split its history and confuse everyone who opens it.
SugarCRM13

Create an Email Template

Action

In MakeCreates a new email template.

Create an Email Template writes a new reusable email into SugarCRM, ready for reps to send from the CRM.

When to use it
marketing drafts and approves message copy in a document tool, and approved versions should become SugarCRM templates without retyping.
Watch out
templates are shared. Give each one a clear, unique name in the mapping so reps can tell the new version from the old.
SugarCRM14

Create an Inbound Email

Action

In MakeCreates a new inbound email.

This action creates an inbound email record in SugarCRM from data your scenario already holds.

When to use it
you manage SugarCRM configuration as a set of records kept outside the CRM and want to recreate them in a fresh instance.
Watch out
make's documentation does not explain what this record controls in SugarCRM. Try it on a test instance and check the result before using it for real.
SugarCRM15

Create an Opportunity

Action

In MakeCreates a new opportunity.

Create an Opportunity adds a deal to your SugarCRM pipeline, with data mapped from earlier modules.

When to use it
a quote request or a demo booking signals real buying intent, and the rep should find the deal already in the pipeline.
Watch out
attach it to an existing account found by a search. An opportunity without its company is easy to lose in reports.
SugarCRM16

Create a Note

Action

In MakeCreates a new note.

This module writes a note on a SugarCRM record, a simple way to bring outside context into the history reps read.

When to use it
after a support call, a survey answer or a payment event, drop a short summary on the account so the next person knows what happened.
Watch out
link the note to its parent record by mapping the identifier. A note with no parent is saved but nobody will find it.
SugarCRM17

Create a Product

Action

In MakeCreates a new product.

Create a Product adds an item to the SugarCRM catalog, so reps can quote it as soon as it exists in your own product source.

When to use it
your shop or inventory tool is where products are born, and SugarCRM should receive each new one without a manual import.
Watch out
create the category, product type and manufacturer first if you use them, otherwise the product lands without its classification.
SugarCRM18

Create a Product Type

Action

In MakeCreates a new product type.

This action adds a product type in SugarCRM, the family label that groups similar items in quotes and reports.

When to use it
a new product family is launched in the catalog you manage elsewhere, and the CRM needs the same family before products are filed under it.
Watch out
run Search Product Types before it. A type created twice splits your reports in two without warning.
SugarCRM19

Create a Project

Action

In MakeCreates a new project.

Create a Project opens a project in SugarCRM, giving delivery work a place right next to the customer who paid for it.

When to use it
an opportunity is won, and the kickoff should exist in the CRM before the account manager even thinks about it.
Watch out
Watch Opportunities fires on every edit, so guard this step, or a deal edited after closing will spawn a second project.
SugarCRM20

Create a Prospect

Action

In MakeCreates a new prospect.

This module adds a prospect to SugarCRM, the stage before a lead, for names you want to reach but have not qualified yet.

When to use it
a list comes out of an event badge scan or a research tool, and marketing wants those people stored in the CRM for later outreach.
Watch out
big lists mean many bundles and many operations. Test with a handful of rows before running the whole file.
SugarCRM21

Create a Revenue Line Item

Action

In MakeCreates a new revenue line item.

Create a Revenue Line Item attaches a product line to a deal in SugarCRM, which turns a vague amount into what is actually sold.

When to use it
a cart or quote built in another tool should appear in the CRM as detailed lines, one per product, under the matching opportunity.
Watch out
a cart with several products needs one run of this module per line, so each line costs its own operation.
SugarCRM22

Create a Campaign

Action

In MakeCreates a new сampaign.

This action sets up a campaign in SugarCRM, so leads and results can be traced back to the right marketing push.

When to use it
campaigns are planned in a marketing calendar or project board, and each one should exist in the CRM before the first lead arrives.
Watch out
reuse the exact campaign name from your planning tool, so later searches match it without guesswork.
SugarCRM23

Delete a Bug

Action

In MakeDeletes a bug.

Delete a Bug removes a bug record from SugarCRM, which keeps the list clean once a report turns out to be noise.

When to use it
a developer closes a ticket as a duplicate in their own tool, and the matching SugarCRM bug should disappear rather than stay open.
Watch out
deletion cannot be undone from Make. Get the bug first and check it is the right one before this module runs.
SugarCRM24

Delete a Call

Action

In MakeDeletes a call.

This module erases a call from SugarCRM, useful when a scheduled call no longer makes sense.

When to use it
a prospect cancels through your booking tool, and the call planned in the CRM should vanish from the rep's list.
Watch out
once deleted, the call is gone from the history too. If you want a trace, change it with Update a Call instead.
SugarCRM25

Delete a Campaign

Action

In MakeDeletes a сampaign.

Delete a Campaign removes a marketing campaign from SugarCRM. Only campaigns are affected, never your company accounts.

When to use it
a draft campaign was created by a test scenario or cancelled before launch, and you want the CRM list tidy.
Watch out
leads may point to that campaign. Check with Get a Campaign before removing it, because Make cannot bring it back.
SugarCRM26

Delete a Case

Action

In MakeDeletes a case.

This action deletes a support case in SugarCRM for good, so spam or test tickets stop cluttering the queue.

When to use it
a spam filter upstream flags a message that already became a case, and support should not have to close it by hand.
Watch out
a real customer request deleted by mistake is lost. Keep the rule strict and run it on test data before switching it on.
SugarCRM27

Delete a Category

Action

In MakeDeletes a category.

Delete a Category removes a product category from SugarCRM when a range is discontinued everywhere else.

When to use it
the tool that owns your catalog retires a category, and the CRM should drop it too instead of offering an empty heading.
Watch out
products may still sit in that category. Move them first with Update a Product, then delete the empty category.
SugarCRM28

Delete a Contact

Action

In MakeDeletes a contact.

This module deletes a person from SugarCRM, which matters when someone asks to be forgotten or a record is pure junk.

When to use it
a privacy request arrives through a form, and the contact must leave the CRM as well as your other tools in one scenario.
Watch out
Search Contacts can return several people with the same name. Delete by the identifier of one exact match, never on a loose search.
SugarCRM29

Delete a Contract

Action

In MakeDeletes a contract.

Delete a Contract takes a contract record out of SugarCRM, typically a draft that was never signed.

When to use it
an e-signature request expires or is declined, and the draft contract created earlier by your scenario should not stay in the account.
Watch out
signed contracts are often records you must keep. Limit this module to drafts your own scenario created.
SugarCRM30

Delete a Currency

Action

In MakeDeletes a currency.

This action removes a currency from SugarCRM when your company stops selling in it.

When to use it
finance retires a currency in its master list, and the CRM should stop offering it on new deals.
Watch out
older deals may still be priced in that currency. Check with Search Opportunities or Get a Currency before deleting admin data that others rely on.
SugarCRM31

Delete a Custom Query

Action

In MakeDeletes a custom query.

Delete a Custom Query removes a saved query from SugarCRM, part of keeping admin settings lean.

When to use it
you clean up queries that a deployment script created for a test, or retire definitions no longer used by any report.
Watch out
a report built on that query stops working once it is gone. Confirm nobody depends on it before the scenario runs.
SugarCRM32

Delete a Forecast Worksheet

Action

In MakeDeletes a forecast worksheet.

This module deletes a forecast worksheet from SugarCRM, for example one created by mistake or by a test run.

When to use it
a scenario you are building filled SugarCRM with test forecasts during Run once, and you want them gone before the sales director looks.
Watch out
forecasts feed management reporting. Deleting a real worksheet changes numbers people already read, so keep this to test data.
SugarCRM33

Delete a Lead

Action

In MakeDeletes a lead.

Delete a Lead removes a lead from SugarCRM, which keeps the pipeline free of fake sign-ups and duplicates.

When to use it
a validation step flags a lead as spam, a disposable address or an obvious bot, and it should leave the CRM before a rep calls it.
Watch out
if Watch Leads runs in another scenario, the lead may already have triggered it. Delete early, before other automations act on it.
SugarCRM34

Delete a Manufacturer

Action

In MakeDeletes a manufacturer.

This action deletes a manufacturer record from SugarCRM when that brand leaves your catalog.

When to use it
purchasing ends a supplier relationship in its own tool, and the CRM should stop listing that brand for new products.
Watch out
existing products may still reference the manufacturer. Reassign them with Update a Product before removing it.
SugarCRM35

Delete a Meeting

Action

In MakeDeletes a meeting.

Delete a Meeting cancels a meeting in SugarCRM by removing it, so calendars and the CRM agree.

When to use it
the prospect cancels through your scheduling tool, and the meeting created earlier by Create a Meeting should disappear from SugarCRM.
Watch out
you need the meeting's identifier, so store it when you create the meeting, or find it with Search Meetings first.
SugarCRM36

Delete an Account

Action

In MakeDeletes an account.

This module deletes a company account from SugarCRM, the heaviest cleanup action on this page.

When to use it
after a merge in another tool, the leftover duplicate account in SugarCRM has to go so reports stop counting the company twice.
Watch out
an account carries contacts, deals and cases. Check what is attached with Get an Account first, because the deletion cannot be reversed from Make.
SugarCRM37

Delete an Email Template

Action

In MakeDeletes an email template.

Delete an Email Template removes an outdated template from SugarCRM, so reps stop sending old wording.

When to use it
marketing marks a message as retired in its content tool, and the CRM template should go at the same time.
Watch out
reps lose the wording for good. Check with Get an Email Template that the scenario picked the right one first.
SugarCRM38

Delete an Inbound Email

Action

In MakeDeletes an inbound email.

This action deletes an inbound email record in SugarCRM, the counterpart of Create an Inbound Email.

When to use it
you remove records that your own setup scenario created on a test instance, so the next test starts from a clean slate.
Watch out
make's documentation does not describe what this record drives inside SugarCRM. Do not point it at a production instance without checking with your admin.
SugarCRM39

Delete an Opportunity

Action

In MakeDeletes an opportunity.

Delete an Opportunity removes a deal from the SugarCRM pipeline, which keeps forecasts honest when a deal was never real.

When to use it
an opportunity was created automatically from a form that turned out to be spam, and it should not inflate the pipeline.
Watch out
lost deals are usually worth keeping for reporting. Change them with Update an Opportunity, and delete only true mistakes.
SugarCRM40

Delete a Note

Action

In MakeDeletes a note.

This module deletes a note from a SugarCRM record, handy when an automation posted something it should not have.

When to use it
a scenario wrote test notes on real accounts during setup, or a note holds data that must be removed after a privacy request.
Watch out
Search Notes may match more notes than you think. Check the bundles with Run once before letting the deletion run on its own.
SugarCRM41

Delete a Product

Action

In MakeDeletes a product.

Removes a product from your SugarCRM catalog from inside a scenario (the automation you build in Make), so a discontinued item stops appearing to the sales team.

When to use it
a product has been retired in the tool that owns your catalog and SugarCRM should follow without anyone deleting it by hand.
Watch out
run it on a test product first with Run once, the editor button that executes the scenario one time, before pointing it at real catalog data.
SugarCRM42

Delete a Product Type

Action

In MakeDeletes a product type.

Clears a product type out of SugarCRM, which keeps the list of types short and readable when your offer changes shape.

When to use it
a family of products no longer exists and its type would only clutter the dropdown the sales team picks from.
Watch out
look at the products filed under that type with Get a Product before deleting it, so nothing ends up without a family.
SugarCRM43

Delete a Project

Action

In MakeDeletes a project.

Takes a project off SugarCRM once it has no reason to stay, so the project list only shows work that is actually alive.

When to use it
a project gets cancelled or archived in your project tool and the CRM copy should disappear along with it.
Watch out
place a filter before this module so only the projects you really mean to remove reach it; every module run on one bundle counts as one operation.
SugarCRM44

Delete a Prospect

Action

In MakeDeletes a prospect.

Erases a prospect record from SugarCRM, useful when a contact asks to be forgotten or when a list import brought in people who never belonged there.

When to use it
an unsubscribe or removal request lands in another tool and the CRM must drop the matching prospect too.
Watch out
prospects and leads are separate records. If the person also exists as a lead, add Delete a Lead to the same scenario.
SugarCRM45

Delete a Revenue Line Item

Action

In MakeDeletes a revenue line item.

Drops a revenue line item from SugarCRM, so the amounts attached to a deal match what the customer really ordered.

When to use it
a line is withdrawn from a quote in your billing or quoting tool and the forecast in SugarCRM should shrink accordingly.
Watch out
this touches figures the sales team reports on. Test the scenario with Run once and read the bundle, one item passed between modules, before switching it on.
SugarCRM46

Get a Bug

Action

In MakeGets a bug.

Fetches one bug with its details from SugarCRM, so the next modules of the scenario can quote its status or description in a message or a ticket.

When to use it
an event elsewhere gives you a bug reference and you need its full content before deciding what to do next.
Watch out
this module reads a single record. To pick bugs by criteria rather than by a known record, use the matching search module of the app instead.
SugarCRM47

Get a Call

Action

In MakeGets a call.

Pulls one logged call out of SugarCRM with everything recorded on it, ready to feed a summary, a follow-up task or a report row.

When to use it
a scenario knows which call it is about, for example from the Watch Calls trigger, and needs details the trigger did not bring.
Watch out
each fetch is one extra operation on your plan. If the trigger bundle already holds what you need, skip this module.
SugarCRM48

Get a Campaign

Action

In MakeGets a сampaign.

Loads one marketing campaign from SugarCRM so its details can travel into a report, a spreadsheet or a message for the marketing team.

When to use it
a lead or a prospect points to a campaign and you want the campaign data next to it in the same scenario.
Watch out
it returns one campaign per run. To go through several campaigns at once, Search Campaigns fits better.
SugarCRM49

Get a Case

Action

In MakeGets a case.

Retrieves a single support case from SugarCRM, handy to show the customer's issue in a chat channel or to enrich a helpdesk ticket.

When to use it
a case reference shows up in an email, a form or another app, and the support team needs the full case before replying.
Watch out
this returns one case only. For a list of open cases, a search module fits better and saves you a loop.
SugarCRM50

Get a Category

Action

In MakeGets a category.

Reads one category from SugarCRM, which lets a scenario turn a bare reference into a name a human can understand.

When to use it
another module hands you a category reference and the message or document you build needs the readable label.
Watch out
categories change rarely, so calling this for every bundle burns operations for the same answer. Fetch it once when you can.
SugarCRM51

Get a Contact

Action

In MakeGets a contact.

Brings back one contact with its full record from SugarCRM, so an email, an invoice or a sync to another tool uses the latest data.

When to use it
you start from a contact reference (a deal, a call, a case) and need the person's details to act on them.
Watch out
when a run goes wrong, open the bundle the module received in the run history first; it usually shows which reference was passed.
SugarCRM52

Get a Contract

Action

In MakeGets a contract.

Opens a single contract from SugarCRM inside the scenario, so its terms or status can be pushed into a document, a reminder or a finance sheet.

When to use it
a signature, renewal or billing event elsewhere refers to a contract and the finance team wants the CRM version at hand.
Watch out
read the bundle after Run once to see which data the module really returns before mapping it further down the scenario.
SugarCRM53

Get a Currency

Action

In MakeGets a currency.

Fetches one currency set up in SugarCRM, which is what a scenario needs to label or convert amounts correctly before passing them on.

When to use it
deals come in several currencies and the report or invoice you generate must show the right one next to each amount.
Watch out
the module reads what SugarCRM holds. Keep the currency settings in the CRM up to date if reports depend on them.
SugarCRM54

Get a Custom Query

Action

In MakeGets a custom query.

Reads one custom query saved in SugarCRM, so a scenario can check its definition or reuse it somewhere else.

When to use it
an admin keeps queries in SugarCRM and wants a scenario to inspect or copy one of them without opening the admin screens.
Watch out
it reads the saved query record. To fetch the records a query matches, look at the search modules or Make an API Call.
SugarCRM55

Get a Lead

Action

In MakeGets a lead.

Grabs one lead from SugarCRM with its current details, ready to route it, score it in another tool or notify the right salesperson.

When to use it
a scenario receives a lead reference, for instance from Watch Leads, and needs fields the trigger bundle does not carry.
Watch out
the lead can change between the trigger and this step. Getting it here gives you the freshest version, at the cost of one operation.
SugarCRM56

Get a Manufacturer

Action

In MakeGets a manufacturer.

Returns one manufacturer from SugarCRM, so a product sheet, a purchase request or a supplier email can carry the right name.

When to use it
you handle products in a scenario and need the maker behind each one before sending anything to a buyer or a supplier.
Watch out
inside a loop over many products, the same manufacturer gets fetched again and again. Group the bundles first if operations count on your plan.
SugarCRM57

Get a Meeting

Action

In MakeGets a meeting.

Loads a single meeting from SugarCRM so its date, attendees or notes can reach a calendar, a reminder or a debrief template.

When to use it
a scenario knows which meeting it is about and must pass its details to a tool the sales team actually checks.
Watch out
the Watch Meetings trigger already sends a bundle per meeting. Add this module only when that bundle misses something you need.
SugarCRM58

Get an Account

Action

In MakeGets an account.

Fetches one company account from SugarCRM, giving the scenario the context around a deal, a case or a contact.

When to use it
an invoice, a ticket or a contract mentions a customer and you want the account record before writing back or alerting someone.
Watch out
an account is the company, a contact is the person. Pick Get a Contact when the step needs a phone number or a first name.
SugarCRM59

Get an Email Template

Action

In MakeGets an email template.

Reads one email template stored in SugarCRM, so the same wording can be reused by a scenario that sends mail through another app.

When to use it
your team writes templates in the CRM and wants a scenario to send them through an email tool without duplicating the text.
Watch out
check with Run once how the template text arrives in the bundle before mapping it into the email you send.
SugarCRM60

Get an Inbound Email

Action

In MakeGets an inbound email.

Retrieves one inbound email record from SugarCRM, so its details can be archived or checked in another tool.

When to use it
an admin wants the content of one inbound email record kept in a shared log outside SugarCRM.
Watch out
read one real example with Run once before mapping: the bundle shows exactly what the module returns for your account.
SugarCRM61

Get an Opportunity

Action

In MakeGets an opportunity.

Loads one opportunity from SugarCRM with its current details, the basis for a deal alert, a forecast line or a handover to finance.

When to use it
a scenario tracks a deal and needs its current state right before posting to a channel or updating another system.
Watch out
opportunities move fast. If several steps depend on the stage, fetch the record once near the start and reuse its bundle.
SugarCRM62

Get a Note

Action

In MakeGets a note.

Fetches one note from SugarCRM, so what a salesperson or support agent wrote can be copied, summarized or shared outside the CRM.

When to use it
a note attached to a contact or a case must follow the record into another tool, like a project board or a chat thread.
Watch out
when a file has to leave SugarCRM along with the note, Save a File is the module that handles files in this app.
SugarCRM63

Get a Product

Action

In MakeGets a product.

Reads one product from the SugarCRM catalog, giving a quote, an order or a stock check the exact product data.

When to use it
an order or a request names a product and the scenario must pull its CRM record before building the next document.
Watch out
this is one product per run. Looping over a big catalog one by one quickly adds up in operations.
SugarCRM64

Get a Product Type

Action

In MakeGets a product type.

Returns one product type from SugarCRM, so a scenario can sort, label or filter products by the family they belong to.

When to use it
a product bundle carries a type reference and the report you build must show the readable name of that type.
Watch out
types change rarely. Fetch each type once rather than asking SugarCRM again for every product.
SugarCRM65

Get a Project

Action

In MakeGets a project.

Pulls one project from SugarCRM, so its status and details can reach a project board, a client update or a delivery checklist.

When to use it
a sale closes and the delivery team works in another tool that needs the project information stored in the CRM.
Watch out
pass a reference that comes from an earlier module, then check with Run once that the right project comes back.
SugarCRM66

Get a Prospect

Action

In MakeGets a prospect.

Retrieves a single prospect from SugarCRM, the record to enrich, qualify or hand to an outreach tool.

When to use it
a list or a form points to a prospect and you need the full record before deciding whether it becomes a lead.
Watch out
prospects and leads are separate records in SugarCRM. Make sure the reference you pass matches a prospect, not a lead.
SugarCRM67

Get a Revenue Line Item

Action

In MakeGets a revenue line item.

Loads one revenue line item from SugarCRM, so the amount and product behind a deal can land in an invoice or a finance sheet.

When to use it
billing needs the detail of a deal line by line, not only the total of the opportunity.
Watch out
an opportunity can carry several line items. Getting them one at a time costs one operation each, so check how many you expect.
SugarCRM68

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Calls any endpoint of the SugarCRM API from a scenario with the same connection as the other modules, which covers what the listed modules do not.

When to use it
you need a record type, an action or a filter that none of the 137 SugarCRM modules offers.
Watch out
you build the request yourself, with no ready-made fields to guide you. Read the SugarCRM API documentation before building it and test with Run once.
SugarCRM69

Save a File

Action

In MakeSaves a file to a temporary folder.

Puts a file coming from SugarCRM into a temporary folder, so the next modules can send it by mail, upload it to storage or attach it elsewhere.

When to use it
a note or a document in the CRM holds a file that has to leave SugarCRM, for instance to reach a shared drive.
Watch out
the folder is temporary. Pass the file to its final destination in the same scenario, and remember the Free plan caps files at 5 MB.
SugarCRM70

Update a Bug

Action

In MakeUpdates a bug.

Changes a bug record in SugarCRM from a scenario, so its status or details stay in step with what the development team does elsewhere.

When to use it
a fix ships in your code tool and the matching bug in the CRM should move forward without a manual edit.
Watch out
only fill the fields you want to change. An empty mapping can overwrite a value someone typed by hand, so test with Run once.
SugarCRM71

Update a Call

Action

In MakeUpdates a call.

Edits a logged call in SugarCRM, handy to add the outcome, change the status or attach a summary produced by another tool.

When to use it
a call ends in your phone or meeting tool and the result must show up on the CRM record the sales team reads.
Watch out
the module needs to know which call to touch. Pass the call reference from Watch Calls or Get a Call rather than guessing it.
SugarCRM72

Update a Campaign

Action

In MakeUpdates a сampaign.

Modifies a campaign in SugarCRM so its status or details reflect what happens in your emailing or ads tool.

When to use it
a campaign starts, pauses or ends in another tool and marketing wants SugarCRM to say the same thing.
Watch out
campaign data often feeds reports. Change a single campaign with Run once first and check the result in SugarCRM before automating it.
SugarCRM73

Update a Case

Action

In MakeUpdates a case.

Updates a support case in SugarCRM, moving its status or adding details as the ticket progresses in your helpdesk or chat tool.

When to use it
a customer replies or an agent closes a ticket elsewhere, and the case in the CRM has to follow.
Watch out
two tools writing to the same case can overwrite each other. Decide which one owns each field before switching the scenario on.
SugarCRM74

Update a Category

Action

In MakeUpdates a category.

Renames or adjusts a category in SugarCRM from a scenario, keeping labels identical to the ones used in your other tools.

When to use it
a category gets renamed in the source of truth, like a catalog or a knowledge base, and the CRM must follow.
Watch out
a renamed category changes what the team sees in SugarCRM. Check with them before an automation starts renaming things.
SugarCRM75

Update a Contact

Action

In MakeUpdates a contact.

Rewrites the details of a contact in SugarCRM, so a new phone number or job title captured elsewhere lands on the right person.

When to use it
a form, a billing tool or an enrichment service learns something new about a contact and the CRM should know it too.
Watch out
if another scenario syncs contacts the other way, the two can bounce the same change back and forth. Pick one direction per field.
SugarCRM76

Update a Contract

Action

In MakeUpdates a contract.

Changes a contract record in SugarCRM, for instance its status after a signature or a renewal handled in another tool.

When to use it
an e-signature or billing event confirms a change and the contract in the CRM must show it without anyone retyping it.
Watch out
contracts matter for finance. Map only the fields the event really changes and leave the rest of the module empty.
SugarCRM77

Update a Currency

Action

In MakeUpdates a currency.

Adjusts a currency set up in SugarCRM, which keeps the way amounts appear in the CRM aligned with your finance tools.

When to use it
finance maintains currency settings in another system and wants SugarCRM to follow without an admin editing it by hand.
Watch out
a change here affects how every amount in that currency appears. Test the scenario on a sandbox account if you have one.
SugarCRM78

Update a Custom Query

Action

In MakeUpdates a custom query.

Edits a custom query saved in SugarCRM, so an admin can keep query definitions consistent from a scenario.

When to use it
several teams rely on the same saved query and its definition is maintained in a document or a sheet outside the CRM.
Watch out
a wrong definition breaks whatever uses the query. Read it first with Get a Custom Query and compare before writing.
SugarCRM79

Update a Lead

Action

In MakeUpdates a lead.

Updates a lead in SugarCRM, moving its status or filling in details as it is qualified by another tool or a person.

When to use it
a scoring tool, a form reply or a meeting booking tells you more about a lead and the sales team should see it in the CRM.
Watch out
if Watch Leads starts the same scenario, updating the lead may start it again. Put a filter so the scenario acts only on the change you care about.
SugarCRM80

Update a Manufacturer

Action

In MakeUpdates a manufacturer.

Edits a manufacturer in SugarCRM, so supplier names and details match the ones your purchasing or catalog tool holds.

When to use it
a supplier changes its name or details in the purchasing system and the CRM must show the same information.
Watch out
test with Run once on one manufacturer and check the result in SugarCRM before letting the scenario touch the whole list.
SugarCRM81

Update a Meeting

Action

In MakeUpdates a meeting.

Keeps a meeting in SugarCRM in step with what changed elsewhere, so the calendar your sales team reads matches the one your booking tool holds.

When to use it
a prospect moves a demo in the scheduling app and the meeting record should follow without anyone retyping it.
Watch out
map only the values that changed; a field you fill with an empty value from the previous module can wipe what the record already had.
SugarCRM82

Update an Account

Action

In MakeUpdates an account.

Rewrites the company record your deals, cases and contacts hang from, so everyone opens the same, current version of the customer.

When to use it
billing data or company details get corrected in your accounting or signup tool and the CRM account should carry the fix.
Watch out
Update an Account needs to know which account to touch; put Search Accounts in front of it when the earlier module only gives you a name.
SugarCRM83

Update an Email Template

Action

In MakeUpdates an email template.

Edits the wording of a template stored in SugarCRM, so the next emails sent from it carry the new text without a manual pass in the admin screens.

When to use it
your marketing team keeps approved copy in a shared doc or table and wants the CRM template refreshed once a version is signed off.
Watch out
every email built on this template after the update uses the new content, so test it with Run once on a template nobody relies on yet.
SugarCRM84

Update an Inbound Email

Action

In MakeUpdates an inbound email.

Changes an inbound email record in SugarCRM from a scenario, without opening the admin screens.

When to use it
your team keeps these records in a sheet outside the CRM and wants SugarCRM to follow each change made there.
Watch out
make's documentation does not say what this record drives in SugarCRM, so check the result with your admin after the first Run once.
SugarCRM85

Update an Opportunity

Action

In MakeUpdates an opportunity.

Moves a deal forward in SugarCRM from another tool: the new details land on the opportunity the moment your scenario runs.

When to use it
a quote gets signed in your e-signature app or a payment clears, and the opportunity should reflect it before the next pipeline review.
Watch out
if the same deal can be updated by two scenarios, the last one to run wins; keep one scenario in charge of each opportunity value.
SugarCRM86

Update a Note

Action

In MakeUpdates a note.

Adds to or corrects a note already attached to a record, so the context your team writes down stays accurate instead of piling up duplicates.

When to use it
a support tool or form sends a follow-up about something already logged, and you prefer one living note over a new one each time.
Watch out
the text you map is what the note ends up saying; if you want to keep the old content, map it from Get a Note and add the new line after it.
SugarCRM87

Update a Product

Action

In MakeUpdates a product.

Pushes new product details into the SugarCRM catalog, so quotes and revenue lines built on that product start from the right information.

When to use it
your e-commerce store or ERP is the master for product data and the CRM catalog should follow each change made there.
Watch out
match products on something stable from the source tool; searching by a name that may change leads the scenario to update the wrong item or none.
SugarCRM88

Update a Product Type

Action

In MakeUpdates a product type.

Renames or adjusts a product type, the family your SugarCRM products are sorted into, so reports and filters keep grouping items correctly.

When to use it
you reorganize your offer in a spreadsheet or catalog tool and want the CRM classification to follow without editing each type by hand.
Watch out
many products can point at one type, so a change here shows up across the catalog; run it once on a test type first.
SugarCRM89

Update a Project

Action

In MakeUpdates a project.

Keeps a SugarCRM project record current when the real work is tracked in another app, so account managers see the right status next to the customer.

When to use it
your delivery team works in a project management tool and each status change there should reach the CRM project the client file links to.
Watch out
the scenario only knows which project to update if you carry a reference between both tools; plan that link before building the flow.
SugarCRM90

Update a Prospect

Action

In MakeUpdates a prospect.

Refreshes a prospect, the not-yet-qualified contact record in SugarCRM, with new details gathered by forms, enrichment tools or events.

When to use it
someone already in your prospect list fills a second form or attends a webinar, and you want the record completed rather than duplicated.
Watch out
pair it with Search Prospects: when the search returns nothing, that person needs Create a Prospect instead, or the update has nothing to act on.
SugarCRM91

Update a Revenue Line Item

Action

In MakeUpdates a revenue line item.

Adjusts a revenue line item, the product-level piece of an opportunity, so forecasts built from those lines stay close to what customers actually buy.

When to use it
quantities or pricing get renegotiated in your quoting or billing tool and the matching line in SugarCRM should carry the new figures.
Watch out
changing a line can shift the totals your forecasts rely on; check who reads those numbers before letting a scenario rewrite them.
SugarCRM92

Search Accounts

Search

In MakeSearches accounts by given criteria.

Finds the company records that match your criteria and hands each one to the next module as a separate bundle, one item that flows through the scenario.

When to use it
before you create or update anything, you need to know whether the customer's company already exists in SugarCRM.
Watch out
a search can return zero, one or several accounts; every module after it runs once per bundle and each run counts as an operation on your plan.
SugarCRM93

Search Bugs

Search

In MakeSearches bugs by given criteria.

Pulls the bug records that fit your filter, so a scenario can act on known product issues instead of someone copying them from the CRM.

When to use it
a support ticket mentions a problem and you want to check whether a matching bug is already logged before opening a new one.
Watch out
when nothing matches, the search returns no bundle and the modules after it do not run; plan what should happen to that ticket if no bug exists yet.
SugarCRM94

Search Calls

Search

In MakeSearches calls by given criteria.

Lists the logged calls that meet your conditions, giving the scenario a batch of call records it can report on, link or pass to another app.

When to use it
you want to send the calls attached to an account to a shared sheet the moment that account changes owner.
Watch out
several calls usually come back at once; if you need them in one message rather than one per call, add an aggregator after the search.
SugarCRM95

Search Campaigns

Search

In MakeSearches campaigns by given criteria.

Looks up the marketing campaigns in SugarCRM that match your criteria, so a lead or contact can be tied to the right one automatically.

When to use it
a form or ad tool sends a campaign name with each signup and the scenario should find the matching campaign before creating the lead.
Watch out
names typed in another tool rarely match the CRM spelling exactly; test the search with Run once on real values from the source.
SugarCRM96

Search Cases

Search

In MakeSearches cases by given criteria.

Returns the support cases that fit your filter, so a scenario can check a customer's open issues before sending a message or creating a new case.

When to use it
a customer writes in through your help desk or a form and you want to see whether a case for them is already in progress.
Watch out
each case found becomes its own bundle; without a filter that narrows the result, a single email could trigger one action per case.
SugarCRM97

Search Categories

Search

In MakeSearches categories by given criteria.

Finds the categories defined in SugarCRM that match what you look for, so other records can be filed under the right one without guessing.

When to use it
an incoming item from another app carries a label and the scenario must turn it into an existing SugarCRM category.
Watch out
if the label has no match, the scenario stops at this module; decide whether to skip the item or create the category with Create a Category.
SugarCRM98

Search Contacts

Search

In MakeSearches contacts by given criteria.

Checks your SugarCRM contacts for people who match the criteria you give, the usual first step before any contact is created or changed.

When to use it
a new email address arrives from a form, a store or a newsletter tool and you want to avoid a second contact for the same person.
Watch out
this is the module that prevents duplicates, but only if the value you search on is reliable; an email address is safer than a full name.
SugarCRM99

Search Contracts

Search

In MakeSearches contracts by given criteria.

Brings back the contracts that meet your conditions, so a scenario can read their details and act on them in other tools.

When to use it
your finance team asks for the contracts of a given account in their spreadsheet whenever that account is updated in the CRM.
Watch out
several contracts can match one account; map carefully which bundle you use downstream, or every one of them goes through the next steps.
SugarCRM100

Search Currencies

Search

In MakeSearches currencies by given criteria.

Finds the currency records set up in SugarCRM that fit your filter, so amounts coming from other tools land with the right currency attached.

When to use it
an order or invoice from another app states its currency and the opportunity you create should use the matching SugarCRM currency.
Watch out
if the source currency is not configured in SugarCRM, the search comes back empty; add it in the CRM before relying on the scenario.
SugarCRM101

Search Custom Queries

Search

In MakeSearches custom queries by given criteria.

Looks through the custom queries saved in SugarCRM and returns those that match, so a scenario can reuse filters your admins already built.

When to use it
you maintain several saved queries and want a scenario to pick the right one by name before working with it.
Watch out
this search returns the saved query records themselves, not the CRM records those queries would list; plan the next module with that in mind.
SugarCRM102

Search Email Templates

Search

In MakeSearches email templates by given criteria.

Returns the email templates that match your criteria, so a scenario can pick the right wording before updating it or passing it to another tool.

When to use it
you keep one template per language or segment and the scenario has to choose one based on data from an earlier module.
Watch out
similar template names can all match a loose filter; name templates clearly in SugarCRM so the search returns the one you expect.
SugarCRM103

Search Forecast Worksheets

Search

In MakeSearches forecast worksheets by given criteria.

Gets the forecast worksheets that fit your filter, giving the scenario the forecast entries your sales managers work from in SugarCRM.

When to use it
you want forecast figures copied to a reporting sheet or a dashboard tool whenever an opportunity changes in the CRM.
Watch out
forecast data can span many rows; aggregate the results before writing them elsewhere, or each worksheet becomes a separate write and a separate operation.
SugarCRM104

Search Inbound Emails

Search

In MakeSearches inbound emails by given criteria.

Lists the inbound email records that match your criteria, so a scenario can check or adjust them.

When to use it
your IT or ops team wants an overview of these records pushed to a shared table without opening the admin panel.
Watch out
pair it with Update an Inbound Email only after reading the bundles with Run once; a loose filter could point the update at the wrong record.
SugarCRM105

Search Leads

Search

In MakeSearches leads by given criteria.

Checks SugarCRM for leads that match the details you pass, so the scenario knows whether to enrich an existing lead or create a fresh one.

When to use it
a demo request arrives from your website form and you want to catch leads your team already has before adding another.
Watch out
leads and contacts are separate records in SugarCRM; a person missing from Search Leads may still exist as a contact, so search both when it matters.
SugarCRM106

Search Manufacturers

Search

In MakeSearches manufacturers by given criteria.

Finds the manufacturer records in SugarCRM that fit your criteria, so products coming from another catalog get tied to the right brand.

When to use it
your supplier feed or store lists a brand for each item and the product you create or update should point to the matching manufacturer.
Watch out
spelling differences between tools lead to empty results; make sure both tools spell the brand the same way before relying on the search.
SugarCRM107

Search Meetings

Search

In MakeSearches meetings by given criteria.

Returns the meetings that meet your conditions, so a scenario can send reminders, fill a report or check a calendar slot against the CRM.

When to use it
a calendar or booking tool reports a change and you want the related SugarCRM meeting before calling Update a Meeting on it.
Watch out
several meetings may share a subject or attendee; narrow the search so the following update does not run on each of them.
SugarCRM108

Search Notes

Search

In MakeSearches notes by given criteria.

Brings up the notes that match your filter, so the context your team recorded in SugarCRM can be read, copied or reviewed from another app.

When to use it
before a renewal call, you want the notes about an account gathered and sent to the rep's inbox or chat tool.
Watch out
each note is its own bundle; send them one by one only if that suits the reader, otherwise group them with an aggregator.
SugarCRM109

Search Opportunities

Search

In MakeSearches opportunities by given criteria.

Finds the deals in SugarCRM that match your criteria, so the scenario can update the right opportunity or report on a slice of the pipeline.

When to use it
a signed quote or a payment comes in and you need the related opportunity before moving it to its next stage.
Watch out
an account can have several open opportunities; filter on something specific to the deal, or the next module acts on every one returned.
SugarCRM110

Search Products

Search

In MakeSearches products by given criteria.

Looks up products in the SugarCRM catalog that fit your filter, so orders or quotes from another tool can be linked to the right catalog item.

When to use it
an online order lists items by reference and you want the matching SugarCRM products before adding revenue line items.
Watch out
when a product is missing from the catalog, the search returns nothing; decide whether the scenario should create it or flag the order.
SugarCRM111

Search Product Types

Search

In MakeSearches product types by given criteria.

Returns the product types that match your criteria, so a new or updated product can be filed under an existing family rather than a guess.

When to use it
your catalog source sends a category label and the scenario has to translate it into a SugarCRM product type.
Watch out
if two types have close names, a broad filter returns both; read the bundles with Run once before mapping the result.
SugarCRM112

Search Projects

Search

In MakeSearches projects by given criteria.

Lists the SugarCRM projects that meet your conditions, so a scenario can keep them aligned with the tool where the delivery work actually happens.

When to use it
a task board or project app reports a change and you need to find which CRM project it belongs to.
Watch out
without a shared reference between both tools, the search has to rely on names; agree on a naming rule with your team first.
SugarCRM113

Search Prospects

Search

In MakeSearches prospects by given criteria.

Checks the prospect list in SugarCRM for records matching your criteria, the step that decides between completing a prospect and creating one.

When to use it
event signups or enrichment results come in and you want to update people already known instead of stacking duplicates.
Watch out
an empty result stops the modules that follow; plan a Create a Prospect step for newcomers so they are not silently dropped.
SugarCRM114

Search Revenue Line Items

Search

In MakeSearches revenue line items by given criteria.

Pulls the revenue line items that fit your filter, the product-level lines of your opportunities, so a scenario can report on them or adjust them.

When to use it
you want the lines of an opportunity copied to a billing or reporting tool when the deal is marked as won.
Watch out
a deal with many lines returns many bundles; aggregate them if the destination expects one document per opportunity.
Need help

Need help automating SugarCRM with Make?

A person reads every message.

FAQ

SugarCRM and Make: common questions

01Is the SugarCRM Make integration free?
Yes, SugarCRM is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Every module run counts as an operation against your monthly credits. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. You still need your own SugarCRM subscription.
02What is needed to connect SugarCRM to Make?
You need an active SugarCRM account with a valid username and password, plus access to the Admin panel to create an OAuth key. In SugarCRM, open Admin, then System, then OAuth Keys, and choose Create OAuth Key from the three-dots menu. Copy the Client ID and the Client secret, then paste them in Make after clicking Create a connection. If you start with a Watch module, click Create a webhook first.
03Does the SugarCRM trigger in Make work in real time?
Yes. All 23 SugarCRM triggers in Make are instant: SugarCRM calls Make through a webhook as soon as a record is created or updated, instead of Make checking on a schedule. That means no clock to set on the first module and no 15-minute wait, even on the Free plan. The flip side is that every edit fires the trigger again, so a record changed five times sends five bundles and spends operations each time.
04What if a SugarCRM module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the SugarCRM API through the same connection, so you can reach records or actions that the 137 listed modules do not cover. You still work inside a normal scenario and can map data from earlier modules. Keep in mind that Make's documentation for this app is flagged as AI-generated, so confirm important details in SugarCRM's own documentation before relying on them.
05Make or n8n for SugarCRM automation?
It depends on the tool your team already builds in. On Make, SugarCRM comes with 137 ready modules, 23 instant triggers and an API call module, all covered on this page. The same app often has a node in n8n as well, so it is worth checking the n8n side if your automations already live there. The n8n vs Make comparison linked earlier on this page lays out the differences between the two tools in detail.