How to add a trigger module on Make
Adding a trigger module in Make starts your scenario by detecting app events or schedules; use instant triggers for real-time or polling for intervals like every 15 minutes. Only one trigger per scenario as the first module with a clock icon; test with Run Once to verify before activating. Common issues like empty bundles are fixed by checking logs and ensuring proper scheduling.
Prerequisites
- Active Make.com account with sufficient operations quota
- Connected app/service accounts (e.g., Google, Slack) via Make's connections
- Scenario turned ON and properly scheduled if using polling triggers
- Basic understanding of instant vs. polling trigger types
- Test authentication in module settings first
Step-by-Step Instructions
Plan your scenario
Watch Records or New Submission to ensure the trigger detects relevant changes.Prepare your apps
Create a new scenario
Add the trigger module
add a module. Select the app/service (e.g., Adobe Workfront, Gmail) and choose a trigger event like Watch Records or New Records Only. The module appears as the leftmost with a clock icon.Create the connection
Configure trigger settings
ID, Name, Project ID. Choose From now on or set starting point for polling.Set scheduling options
Turn scenario ON
Test the trigger
Run Once to execute manually and verify data bundles. Check execution logs for bundles, errors, or empty runs before full activation.Save and monitor
Common Issues & Troubleshooting
Empty check runs or no bundles in polling triggers
Verify schedule is ON and interval (e.g., 15 min); check History logs for data detection. Adjust 'Choose where to start' to <code>From now on</code> or increase max items.
Instant triggers not firing (no errors)
Confirm webhook creation and service connection; test with manual event. Reschedule if queued; contact support for backend issues.
Auto runs differ from manual Run Once
Check execution logs in History for bundle counts/errors. Ensure filters match real events; toggle OFF/ON to reset.
Cannot add second trigger
Triggers allowed only once as first module. Delete existing via right-click if needed, then add new one.
Auth or connection failures
Re-authenticate in module settings; test connection separately. Verify API tokens/permissions for the app.