Skip to main content
NextLevel MCA adds its own triggers to your CRM’s workflow builder, so your CRM workflows can react to what happens on a deal: send a text when a lender approves, tag a contact when contracts come back, start a renewal campaign at 50% paid, and so on. Anyone who can build workflows in your CRM can use them.

​
Use a trigger in a workflow

1

Open a workflow in your CRM

Create a workflow, or open an existing one, and click Add New Trigger.
2

Pick a NextLevel MCA trigger

Search for the trigger name, for example Submission Event.
3

Set its filters

Most triggers have filters, such as Status or Activity. Leave a filter empty to fire on everything, or pick values to fire only on those.
4

Use its data in later steps

Each trigger carries values, such as Business Name or Lender Name, that you can insert into texts, emails, tags and conditions later in the workflow.
5

Publish the workflow

The trigger starts firing once the workflow is published.
Every trigger runs on the deal’s CRM contact (Contact ID), so the workflow acts on the merchant.

​
The triggers

​
Submission Event

Fires whenever a submission to a lender changes status: created, sent, approved, declined, needs more information, funded, expired or withdrawn. That includes replies NextLevel MCA reads from lender emails and updates from lenders connected by API.
  • Filters: Status, Lender(s), AI Classified (true when the status came from reading a lender’s email).
  • Data: business name, lender name, status, decline reason and category, the items a lender asked for, when it was submitted and answered, and, on an approval, the offer amount, rate, payback, payment amount, payment frequency and term.
Example: filter Status to Needs info to text the merchant the list of items the lender wants.

​
Portal Activity

Fires when the merchant does something in the merchant portal: accepts an offer, declines an offer, uploads documents, signs the application, or returns signed contracts. A batch of uploads fires once, not once per file.
  • Filter: Activity (Accepted an offer, Declined an offer, Uploaded documents, Signed the application, Returned signed contracts).
  • Data: business name, activity, offer amount, document name, signer name, decline reason, the rep’s name and email, and when it happened.

​
Contracts

Fires when a lender replies with the contracts (they’re saved to the deal automatically) and when the merchant uploads signed contracts in the portal.
  • Filter: Event (Received from lender, Signed by merchant).
  • Data: business name, event, lender name, the files, document name, the rep’s name and email, and when it happened.

​
Application Abandoned

Fires once, 30 minutes after a merchant stops filling in your online application without submitting it. See Unfinished applications.
  • Filter: Texting consent (Yes or No). Only text merchants who said yes.
  • Data: the owner’s first and last name, email and phone, business name, how far they got (Progress (%)), texting consent, a Resume Link that reopens their application where they left off, the rep’s name and email, and when they started and last typed.

​
Document Request Sent

Fires when a document request is first sent, by email or by text, and as the documents come in: received partial once when the first requested document arrives, received complete once when everything on the request is in. Documents count however they arrive: uploaded in the portal, emailed back, matched by hand, or found by the bank statement check. When one upload completes several open requests at once, it fires once.
  • Filters: Event Type (sent, received partial, received complete) and Documents Requested.
  • Data: business name, owner email, the documents requested, received and still pending, percent complete, the latest document received, who sent the request, and when.

​
Deal Funded

Fires when a deal is marked funded and its advance is created. See Marking a deal funded.
  • Filters: Lender and Payment Frequency.
  • Data: business name, lender name, funded amount, factor rate, payback, payment frequency, term, lender commission amount and funding date.

​
Advance Status

Fires when a funded advance crosses a paid-down milestone: 5%, 10%, 15% and so on up to 100%. Each milestone fires once per advance, when a payment is recorded that crosses it. Useful for renewal outreach. See Renewals.
  • Filters: Percent Paid and Lender.
  • Data: business name, lender name, funded amount, payback, amount paid, remaining balance, percent paid, status, funding date and when the milestone was reached.

​
Deal Passed

Fires when an approved deal that hasn’t funded is passed from one rep to another, automatically by Passes or by hand.
  • Filter: Pass Count.
  • Data: business name, the rep it came from (name and email), the rep it went to, the original rep, and days since approval.

​
New Deal

Fires when a deal is created in NextLevel MCA.
  • Filter: Paper Grade.
  • Data: business name, the owner’s name, email and phone, requested amount, monthly revenue and paper grade.

​
Common problems

NextLevel MCA must be installed on your CRM account, and your CRM account must allow premium workflow triggers and actions. If you still don’t see them, ask whoever manages your CRM account.
Check the workflow is published and its filters match what happened. Every trigger acts on the deal’s CRM contact, so a deal with no linked CRM contact has no one for the workflow to run on.
That’s a different feature: pipeline stages move on their own when events happen inside NextLevel MCA. See Pipeline stage events.