GetCourse Connector

Automate support dialogs, use learner context, and keep GetCourse conversations organized when learner messages arrive.

Overview

GetCourse flows are triggered by events from your school account - typically when a learner opens a support dialog or sends a message. A flow can read the incoming message, use your knowledge base or LLM prompts, look up learner data, and take follow-up actions in GetCourse.

Setup

Open the GetCourse Integration guide first, complete the connection settings, then create and activate a flow with the GetCourse trigger.

Entry and exit nodes

  • GetCourse Input - reads the incoming GetCourse event into flow variables such as the learner message, dialog information, event type, learner ID, name, and email
  • GetCourse Response - sends the final text reply back to the related support dialog

GetCourse action nodes

Dedicated nodes let a flow use learner context, update dialog state, and keep support conversations tidy.

User data

  • Get User groups - check group membership before choosing a branch or answer
  • Get User deals - fetch the learner's deals/orders for sales or billing context
  • Get User trainings - see which trainings are available to the learner
  • Get User purchases - include purchase history in routing or support decisions
  • Get User metadata - map profile fields into flow variables

User actions

  • Add user to group - add the learner to a GetCourse group by ID
  • Remove user from group - remove the learner from a GetCourse group by ID

Dialog actions

  • Change Department - move a dialog to another department
  • Add note to dialog - save an internal note on the dialog
  • Close dialogue - close a dialog after the issue is resolved
  • Get dialogue messages - fetch recent dialog history as text
  • Is dialog safe for bot? - stop or branch when a manager or another person has joined the dialog

Several action nodes can branch to true or false paths based on the GetCourse result.

Common scenarios

  • Auto-reply in a new support dialog with RAG-backed answers
  • Route dialogs to a department based on message content or user groups
  • Use purchases, trainings, or group membership to choose the right answer or route
  • Close the dialog automatically after the issue is resolved

Nodes you can combine

Any GetCourse flow can also use AI nodes such as RAG Search and Invoke LLM, control nodes such as conditions and filters, data nodes such as variables and text operations, HTTP requests, and debug nodes alongside GetCourse actions.

Notes

  • Paused flows waiting for user input expire after 24 hours.
  • Currently enabled GetCourse events are primarily incoming message types; more event types may be added over time.
  • Store GetCourse keys in integration settings or secret flow variables so they stay masked in execution logs.

Coming soon: per-node configuration reference, field descriptions, and step-by-step flow examples.