Zapier triggers, actions, and data reference

In this article: Every trigger, action, and search available in the Ruzuku-Zapier integration — what data each one sends, filtering options, and automation ideas. All Plans

Ruzuku's Zapier integration includes 7 triggers (events in Ruzuku that start a Zap), 2 actions (things Zapier can do in Ruzuku), and 1 search (look up student data). This article covers each one in detail. If you're new to Zapier, their key concepts guide explains how triggers, actions, and Zaps work together.

If you haven't connected Ruzuku to Zapier yet, start with Set up Zapier integration. For an overview of common automations, see Connect Ruzuku with Zapier.

At a glance

Triggers

Triggers are events in Ruzuku that start a Zap. When the event happens, Ruzuku instantly sends data to Zapier, which passes it to whatever app you've connected.

New Student Enrolled

Fires when a student enrolls in one of your courses — whether through a paid purchase, free invitation, or manual enrollment.

When to use it: This is the most popular trigger. Use it to sync new students to your email list, log enrollments to a spreadsheet, or send yourself a notification.

Data sent to Zapier:

• Student name, email, timezone, bio, and profile photo URL
• Custom profile fields (if your site uses them)
• Course name and ID
• Price point name and amount (e.g., "Premium Package — $95 USD")
• Purchase ID, price ID, and coupon ID (if a coupon was used)
• Enrollment date

Filtering: You can choose up to 10 specific courses. If you don't select any, the trigger fires for enrollments across all your courses.

Example automations:

• New Student Enrolled → ConvertKit: Add Subscriber — Tag students by course so you can send targeted follow-ups.
• New Student Enrolled → Google Sheets: Create Row — Log every enrollment with the price point and amount for revenue tracking.
• New Student Enrolled → Slack: Send Message — Get a real-time notification in your team channel during a launch.

Lesson Completed

Fires when a student marks a lesson as complete.

When to use it: Track individual lesson progress, send encouragement at key milestones, or trigger drip content in another tool.

Data sent to Zapier:

• Student name, email, and ID
• Lesson title and ID
• Course title and ID
• Completion date

Filtering: Select a specific course (required). You can optionally filter to a single lesson — useful if you only care about completion of a key lesson, like a final project.

Example automations:

• Lesson Completed → Gmail: Send Email — Send a congratulations email when students finish your most important lesson.
• Lesson Completed → Airtable: Create Record — Build a detailed progress log for reporting to an organization or employer.

Course Completed

Fires when a student completes all lessons in a course.

When to use it: Trigger follow-up sequences, request testimonials, offer the next course, or log completions for compliance reporting.

Data sent to Zapier:

• Student name, email, and ID
• Course title and ID
• Completion date

Filtering: Select a specific course.

Example automations:

• Course Completed → ConvertKit: Add Tag — Tag completers so you can send a follow-up sequence with a testimonial request or advanced course offer.
• Course Completed → HubSpot: Create Contact — Add course graduates to your CRM with a "completed" status for sales follow-up.

Quiz Submitted

Fires when a student submits a quiz in one of your lessons.

When to use it: Track quiz performance, flag students who may need help, or log assessment results for compliance.

Data sent to Zapier:

• Quiz score (0–100)
• Student name, email, and ID
• Lesson title and ID
• Course title and ID
• Submission date

Filtering: Select a specific course (required). You can optionally filter to a single lesson.

Example automations:

• Quiz Submitted → Google Sheets: Create Row — Build a gradebook spreadsheet with scores, student names, and dates.
• Quiz Submitted → Gmail: Send Email (with Zapier filter: score < 70) — Automatically email students who score below a threshold, offering extra resources or a chance to retake.

Assignment Submitted

Fires when a student submits an assignment in one of your lessons.

When to use it: Get notified when assignments come in so you can review them promptly, or log submissions for tracking.

Data sent to Zapier:

• Assignment questions and the student's answers (each question-answer pair)
• Student name, email, and ID
• Lesson title and ID
• Course title and ID
• Submission date

Filtering: Select a specific course (required). You can optionally filter to a single lesson.

Example automations:

• Assignment Submitted → Slack: Send Message — Get a Slack notification with the student's answers so you can review and respond quickly.
• Assignment Submitted → Google Sheets: Create Row — Log all submissions in a spreadsheet for batch review.

Comment Posted

Fires when a student (or you) posts a comment in a lesson discussion.

When to use it: Stay on top of discussions without checking Ruzuku constantly, or archive discussion activity in another tool.

Data sent to Zapier:

• Comment text (HTML stripped)
• Whether it's a reply to another comment (parent comment ID)
• Discussion prompt text
• File attachments (URLs)
• Student name, email, and ID
• Lesson title and ID
• Course title and ID
• Post date

Filtering: Select a specific course (required). You can optionally filter to a single lesson.

Example automations:

• Comment Posted → Slack: Send Message — Stream discussion activity into a Slack channel so your team can monitor engagement.
• Comment Posted → Email: Send Email (with Zapier filter: specific lesson) — Get notified when students respond to a particular discussion prompt.

Subscription Canceled

Fires when a student cancels their subscription (recurring payment plan) for one of your courses.

When to use it: Follow up with students who cancel, update your CRM, or track churn.

Data sent to Zapier:

• Student name, email, timezone, bio, and profile photo URL
• Custom profile fields
• Course title and ID
• Purchase ID, price ID, and coupon ID
• Price point name
• Cancellation date

Filtering: You can choose specific courses. If you don't select any, the trigger fires for cancellations across all your courses.

Example automations:

• Subscription Canceled → Gmail: Send Email — Send a personal follow-up asking what you could improve (or offering a discounted rate to return).
• Subscription Canceled → Google Sheets: Create Row — Track cancellations alongside enrollment data to monitor churn by course.
• Subscription Canceled → ConvertKit: Add Tag — Tag canceled subscribers so you can send a win-back email sequence.

Actions

Actions are things Zapier can do in Ruzuku. These let other apps trigger enrollments and student management in your courses.

Enroll a Student

Enrolls a student in one of your courses. If the student doesn't have a Ruzuku account yet, one is created automatically and they receive a welcome email with a login link.

Fields you provide:

• Course (required) — which course to enroll them in
• Email (required) — the student's email address
• Name (required) — the student's name

What happens:

1. If the email matches an existing Ruzuku account, that person is enrolled in the course.
2. If the email is new, Ruzuku creates an account and sends a welcome email with a one-click login link.
3. The student appears in your Manage Course → Students list.

Example automations:

• Typeform: New Entry → Ruzuku: Enroll a Student — Automatically enroll people who fill out an application form.
• Stripe: New Payment → Ruzuku: Enroll a Student — If you sell through a separate checkout (outside Ruzuku's built-in price points), enroll buyers automatically.
• Google Sheets: New Row → Ruzuku: Enroll a Student — Bulk enroll students by adding rows to a spreadsheet.

Unenroll a Student

Removes a student's access to a course. The student's account isn't deleted — they just lose access to the specific course.

Fields you provide:

• Course (required) — which course to unenroll them from
• Email or User ID — identify the student (provide at least one)

Example automations:

• Stripe: Subscription Canceled → Ruzuku: Unenroll a Student — If you manage billing outside Ruzuku, automatically remove access when a subscription ends.
• Use alongside the Enroll a Student action for time-limited access managed by external tools.

Search

Find a Student

Looks up a student in your Ruzuku account by email address or user ID. This is most useful as a middle step in multi-step Zaps — for example, finding a student's Ruzuku user ID before using it in an Unenroll action.

Search by: Email address or User ID (provide at least one)

Returns: Student name, email, timezone, bio, profile photo URL, and custom profile fields.

Filtering tips

Most triggers let you narrow down which events fire your Zap:

• Course filtering is available on all triggers. Some require you to pick a course; others (enrollment and cancellation) optionally let you select up to 10 courses or leave it open for all courses.
• Lesson filtering is available on Lesson Completed, Quiz Submitted, Assignment Submitted, and Comment Posted — but only when you've selected a single course.
• Zapier's built-in filter step can add conditions on any data field. For example, fire only when the quiz score is below 70, or only when the price amount contains "USD."

Browse all Ruzuku integrations on Zapier to see pre-built templates you can use as a starting point.

Frequently Asked Questions

Related Articles

Need Help?

Email us at support@ruzuku.com — we typically respond within a few hours (M–F 10am–6pm ET). We can help with connecting your Ruzuku account to Zapier and understanding the available triggers. For help building specific Zaps, Zapier's support team is the best resource.