Short walkthroughs that turn the platform into your operations team: automated pipelines, instant follow-ups, AI-handled admin. One video, one less thing to do manually.
How to use the Create Opportunity automation action to spawn new opportunities automatically — perfect for recurring workflows like weekly gig bookings, retainers, or any business with fixed recurring jobs.
The Create Opportunity action lets an automation spawn a brand-new opportunity — on a schedule, on a trigger, or as part of a larger workflow — without any manual input. It is the platform-native answer to recurring spawn workflows that previously required an external script.
Think about a business that runs the same job week after week for the same clients. A trivia events company with 20 venues, for example, needs a fresh opportunity created every Monday for each venue with the host-pay product attached. Before Create Opportunity, that meant a Python script running outside TrustPager. Now it is a single Auto Schedule + automation, entirely inside the platform.
The same pattern applies to:
TrustPager has two actions for creating opportunities. They are designed for opposite situations:
Rule of thumb: if the customer already exists in your CRM, use Create Opportunity. If you are handling a fresh inbound enquiry, use Create Lead.
Required fields are marked. Everything else is optional and can be left blank.
{{today}}.The name field supports template tokens that resolve against the pinned customer and primary contact at the time the action runs:
{{customer.name}} — the account name{{contact.first_name}} — the primary contact's first name{{today}} — today's date (e.g. 2026-05-04){{now}} — the current date and timeExample: "{{customer.name}} — Week of {{today}}" produces "Riverside Hotel — Week of 2026-05-05" when the schedule fires each Monday.
See the full token reference at https://trustpager.com/help-center/first-name-only-contacts.
A trivia events business runs 20 venues, each with a fixed weekly host. Every Monday morning a fresh opportunity should appear for each (venue, host) pair with the host-pay product attached.
{{customer.name}} — Week of {{today}}When the action runs inside an Auto Schedule with an Opportunities or Contacts audience, the Customer and primary Contact fields auto-fill from the row that triggered the run — even if you left those fields blank in the action config. This is what makes the per-row spawn pattern work without manually listing every customer ID.
If you hard-code a Customer or Contact in the action config, those values take precedence over the trigger context.
Create Opportunity validates all IDs before inserting. If a pipeline, stage, customer, contact, or product ID does not belong to your workspace, the action throws a clear error rather than creating an orphan record. Check the automation run log at https://app.trustpager.com/auto/errors if an action fails — the error message will name the offending field.
Talk to Evie right now, or book a real human for a deeper walkthrough. Whichever feels right.
Hear her in 10 seconds.

60 minutes with a real human · Google Meet · Free.