Make

Lineup Ninja can trigger events in Make when you publish your event.

What triggers are available and when do they fire?

The following triggers are available

• Watch Speaker
• Watch Session
• Watch Label
• Watch Location
• Watch Track
• Watch Resource

Triggers fire when you publish your agenda via the ‘Publish Agenda’ page. They do NOT fire as you update your agenda in ‘Agenda Planning’.

This means you can work in ‘Agenda Planning’ until you are ready to publish your changes. When you are ready, you publish the data to Make to fire the triggers.

What data is available in the trigger?

In the default configuration the data in the trigger includes the data for the object itself and related data that might be useful in a future step. For example the data for Watch Speaker trigger includes the following:

• The speaker’s attributes (First Name, Last Name, Bio etc…)
• The speaker’s sessions. And for each session:
  • The session name, description etc
  • The session location
  • The session tracks, and for each track:
    • The track name
  • The session labels, and for each label:
    • The label name
• The speaker’s labels, and for label:
  • The label name

If you do not want to include the related data, you can configure the “Should related data be included” option in the integration configuration.

You can download the Interface for each type from these links:

• Speaker
• Session
• Label
• Location
• Resource
• Track

What data is used for sample / test data

When configuring your Scenario you may see sample data, this is designed to include all the fields you are likely to see.

You can download the sample data for each type from these links:

• Speaker
• Session
• Label
• Location
• Resource
• Track

What's the difference between 'Id' and 'Lineup Ninja Id' and 'Lineup Ninja Short Id?

In the trigger you will find each object has three identifiers

• ‘id’ or ‘Make Id’ - This is an identifier used to cause the trigger to fire. It may change and should not be used in a subsequent step.
• ‘lineupNinjaId’ or ‘Lineup Ninja Id’ - This is a fixed identifier and does not change. You should use this identifier if you need a consistent identifier in your following steps.
• ‘lineupNinjaShortId’ or ‘Lineup Ninja Short Id’ - This is the first 8 characters of the UUID for the object. It can use used when a full UUID is too long to fit into a subsequent step

Create the integration

Creating a Make integration requires configuration on both the Lineup Ninja and Make sides.

Start in Lineup Ninja by following these steps:

• Click the ‘Publish Agenda’ menu item.
• Scroll down to ‘Make’ and press ‘Integrate’
• In the configuration that is displayed you can set some options for how the data is shared with Make. You can start with the defaults, but please do read all of the documentation because these options affect the number of Make Tasks that will be used, which will have cost implications for you:
  • Should related data be included
• Click ‘Save’
• Click ‘Publish’
• You will now see a table containing ‘Username’, ‘Password, ‘Team Id’ and ‘Publication Id’.

You are now ready to configure Make.

• Open Make in a new tab.
• Create a new Scenario
• Click the big + and choose ‘Lineup Ninja Agenda Publishing’
• Choose the Trigger you want
• Choose / Create the connection. This is where you will input the ‘Username’, ‘Password, ‘Team Id’, and ‘Publication Id’,
• Choose how many objects to process per cycle.
• Click Ok and add your subsequent steps.

Publishing your schedule

To publish your schedule just click the ‘Publish’ button!

How long does it take for Scenarios to fire?

Make looks for new data in your Lineup Ninja event on a regular schedule. The frequency depends on your configuration in the Make scenario.

How do I use 'related data' in a Scenario?

As explained above, the data available in the trigger contains related data that might be useful. For example a ‘Speaker’ contains a list, known as an array, of ‘Sessions’ containing the details for each of their sessions.

How you use this data depends on the action you will use. Some actions support arrays natively and you will be able to pass the data directly to the action.

Some actions do not support arrays. In this instance you can use the ‘Iterator’ flow control tool to run an action once for each item in the array

For example if you want to trigger an action for each Session a Speaker is presenting you can add an ‘Iterator’ step. Then you can choose the fields from the related data you want to make available in the next step. The ‘Iterator’ can be found in the ‘Flow Control’ tools at the bottom of the screen

You can find more information about ‘Iterators’ in the Make Documentation.

Can I create multiple Make integrations?

Yes you can create multiple Make integrations. Some reasons you might want to do this:

• To trigger Scenarios at different times. For example you might want to publish some changes to Scenarios every day, and to some other Scenarios once per week.
• To send different content to different Scenarios. You can do this by applying different ‘Session’ and ‘Speaker’ filters to each integration.

How do I use Custom Field data?

You can add Custom Fields to your event. These will be available in the Make feed.

The object has a ‘Custom Fields’ array that contains one item per custom field that has a value set for that object.

For example a Speaker may have multiple items in ‘Custom Field Data’ eg

Custom Field Data - Field Name: 'Number of Hotel Nights'
Custom Field Data - Field Type: number
Custom Field Data - Field Value: 3

and

Custom Field Data - Field Name: 'Short Bio'
Custom Field Data - Field Type: text
Custom Field Data - Field Value: 'Super great presenter'

If you need to extract the data for a specific field you can use the ‘Set Variable’ tool in Make. A full video overview is available here. In short you can do this:

• Add ‘Set Variable’ from Tools
• Entry a name
• Leave the default of ‘One Cycle’ for ‘Variable Lifetime’.
• Then use this formula, replacing “Test Field” with the name of the Custom Field you want to use. {{get(map(1.customFieldData; "value"; "fieldName"; "Test Field"); 1)}}
• The data is then available for use in subsequent steps.

What this does is

• Takes the value of the ‘customField’ data from the first step
• Extracts the value field from each item, where fieldName is Test Field
• Returns the first result. Custom Field names must be unique in Lineup Ninja so there can only ever be one result at most.

How can I filter the published content?