Skip to content

Integration overview

Once a slide answers well in Try it, you connect it to your course. This page explains the two interfaces and eight destinations SlideMind supports, where to get the integration code, and the rules that apply everywhere. It is written for course authors who install slides in an authoring tool, an LMS or a web page.

Every slide runs through one of two interfaces. You choose it with the destination.

  • Authoring tool interface (shown as Authoring tool in the Activity and destination dialog). You build the screen yourself in your authoring tool: a text entry field, a button, a text box. The integration code is JavaScript. It reads the learner’s text from an authoring tool variable, sends it to SlideMind, and writes the reply back into another variable. You keep full control of the design and can branch on the results.
  • SlideMind widget. SlideMind provides the screen: a ready-made Q&A or Chat panel that you embed in your course. You style it in the slide’s Look step, it can show an AI notice, and its texts follow the Learner language.
Destination (as shown in SlideMind)InterfaceWhat you installStatusGuide
Articulate StorylineAuthoring toolA ready-made slide (.story) to import, or JavaScript in an Execute JavaScript triggerStableArticulate Storyline (JavaScript)
Adobe CaptivateAuthoring toolJavaScript in an Execute JavaScript actionBetaAdobe Captivate
LectoraAuthoring toolJavaScript in a JavaScript actionBetaLectora
dominKnow | ONEAuthoring toolJavaScript in a JavaScript actionBetadominKnow | ONE
iSpring SuiteAuthoring toolJavaScript connected to your course variablesBetaiSpring Suite
Articulate Storyline (Web Object)SlideMind widgetA folder (.zip) inserted as a Web ObjectStableArticulate Storyline (Web Object)
Articulate Rise 360 (Code block)SlideMind widgetAn HTML snippet pasted into a Code blockStableArticulate Rise 360
HTML Widget (iframe)SlideMind widgetAn <iframe> pasted into a page or an HTML blockStableHTML widget (iframe)

Storyline appears twice on purpose. With the JavaScript destination the screen is a Storyline slide: a ready-made one, or your own. With the Web Object destination you insert the SlideMind widget and skip the JavaScript.

Authoring tool code (5 tools)Storyline Web ObjectRise 360 Code blockHTML widget
Q&A and ChatYesYesYesYes
CaptureYesUses the Storyline JavaScript codeAdvanced onlyAdvanced only
Values sent from the authoring toolYesNoNoNo
Structured results in a Q&AEach field in its own variableEach field in a Storyline variableScore and verdict shown in the widgetScore and verdict shown in the widget
Structured results in a ChatEach field in its own variableEach field in a Storyline variableNo, the Chat answers in plain textNo, the Chat answers in plain text
AI noticeNo, inform learners on your own screenYesYesYes
Appearance, Q&A layouts, learner languageYour own designYesYesYes
”Activity finished” signal…_done variable (Chat)…_done variableSet completion requirements in RiseA message to the parent page (advanced)

“Advanced only” means the capture relies on messages sent by the page around the widget, which only a developer can set up. See HTML widget (iframe).

You pick the destination when you create a slide, and you can change it later:

  1. Open the slide in the slide editor.
  2. In the Activity box, select Change. The Activity and destination dialog opens.
  3. Choose the activity (Q&A, Chat or Memory capture).
  4. Under Interface, choose Authoring tool or SlideMind widget. For a Capture slide, the field is called Integration method, with Authoring tool connection or Embedded capture.
  5. Under Destination, choose your tool, then select Done.

The Activity and destination dialog, with the question-and-answer, Chat and Memory capture choices and the Interface and Destination menus

New slides start with the workspace default: Settings › Integrations › Default editor. Only the workspace Owner can change it.

The last step of the slide editor is Installation. Its title names your destination, for example “Set it up in Captivate” or “Add it to Rise 360”.

  1. Open the slide and go to the Installation step.
  2. If you see This slide is not published yet, select Publish (or Save and publish when you have unsaved changes). Your course gets no answer from a draft.
  3. Follow the Setup steps listed for your destination. The variable names in the steps are shown exactly as you paste them in your authoring tool: click a name to copy it.
  4. For the authoring tool interface and the Storyline Web Object, check the variable names. Rename them now if you want, before the first copy.
  5. Select Copy the code, then paste the code in your authoring tool or page.

Two destinations start with a ready-made download instead:

  • Articulate Storyline, for a Q&A or a Chat: the Ready-made Storyline slide card offers Download the slide (.story), a slide to import into your Storyline project. The setup steps and Copy the code move to the Manual setup section, and the variable names to Storyline variables. See Articulate Storyline (JavaScript).
  • Articulate Storyline (Web Object): the Ready-made Web Object card offers Download the folder (.zip), a folder to insert as a Web Object. See Articulate Storyline (Web Object).

The Add it to Storyline step of a published Storyline slide: the Ready-made Storyline slide card with the Download the slide (.story) button, the closed Manual setup and Storyline variables sections, and the link to the full guide

If the slide has unsaved changes, the button reads Save & copy the code (or Save & download the slide, Save & download the folder): it saves the slide first. The code is always Built from the saved slide. To read it before you copy it, open Show the code.

Under the steps, Read the full guide for … opens the guide of your destination on this site. The step ends with links to when to copy the code again and to the go-live checklist.

Publishing a slide and renaming its variables need the Owner or Editor role.

On the Slides page, open the ⋯ menu at the end of a slide’s row:

  • Copy the … code copies the code directly. The item names the destination, for example Copy the Articulate Storyline code or Copy the HTML Widget (iframe) code.
  • For a Storyline Web Object, Download the Articulate Storyline (Web Object) folder downloads the folder instead.
  • Installation steps opens the slide’s Installation step.

The shortcut uses the slide’s own destination and activity, or the workspace Default editor when the slide has none. It copies the code of the saved slide. Your course gets no answer until the slide is published.

  1. Publish the slide. Only a published slide answers. A draft or archived slide gets no answer in your course.
  2. Test in the published course. Authoring tool previews do not always run JavaScript, and they never identify the learner. Test in your LMS or in SCORM Cloud. See Test before going live.
  3. Know what needs a new copy. Most changes apply to your course as soon as you save the slide. A few are frozen in the installed code and need a new copy or a new download. See Changing a slide after installation.
  • Connect the AI. Q&A and Chat slides need SlideMind Credits or your own provider key. See Choosing how AI is funded.
  • List your allowed websites. Add the addresses of your LMS and course hosting in Settings › Integrations › Allowed origins. See Allowed websites.
  • Plan how learners are identified. Learner memory works only for a learner the LMS (or an sm_user parameter) identifies. See Identifying learners.
  • Mind the language. The AI replies in the language of your instructions. The widget’s Learner language only sets the buttons, labels and messages around the reply. See Appearance and language.