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:

•    In Lineup Ninja, navigate to Agenda Planning  > Publish Agenda
• 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 ‘Custom Field’ 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?

You can filter which Speakers and Sessions will be published based on a number of criteria. Some common use cases for filters are:

• Preventing ‘Placeholder’ sessions from being published
• Holding back a Speaker who is not yet ready to be announced
• Excluding sessions scheduled during the ‘build up’ day for the event
• Only publishing speakers who have confirmed their slot
• Removing a particular location, or track from the published schedule
• Anything you can think of using labels!

For Speakers you can filter in 3 ways

• Choose which speakers are to be published based on their relationship to sessions
  • (If Speaker Confirmation is enabled): Publish speakers that have a confirmed session that is published and not filtered out.
  • Publish speakers that are speaking on any session that is published and not filtered out.
  • Publish all speakers
  • Publish no speakers
• Apply more granular filters with labels
  • Only publish speakers with a particular label. For example you might want to use a ‘Content Reviewed’ label to flag speakers that have had their content reviewed.
  • Exclude speakers with a particular label. For example you might want to exclude a ‘Do not publish’ label to prevent publishing of speakers who are not yet ready to be published.

For Sessions you can filter in numerous ways

• Choose which sessions are to be published based on their relationship to speakers
  • Publish All Scheduled Sessions. Publishes sessions regardless of whether they have confirmed speakers or not.
  • (If Speaker Confirmation is enabled): Publish sessions that have one confirmed speaker.
  • (If Speaker Confirmation is enabled): Publish sessions that have all their speakers confirmed.
  • Publish All Sessions (available on Lineup Ninja Agenda App only)
• Apply filters with labels
  • Only publish sessions with a particular label. For example you might want to use a ‘Content Reviewed’ label to flag sessions that have had their content reviewed.
  • Exclude session with a particular label. For example you might want to exclude a ‘Placeholder’ label to prevent publishing of sessions which are not yet populated.
• Filter by location
  • Only publish sessions in a particular location, or locations. This can be useful if you are publishing an agenda for just one or two locations.
  • Exclude sessions in a particular location, or locations. This can be useful if you have scheduled sessions in your Green Room or similar back stage location.
• Filter by resource
  • Only publish sessions needing a particular resource. This could be useful if you are producing an agenda for a particular team that manages some resources.
  • Exclude sessions needing a particular resource.
• Filter by Date
  • Only publish sessions in a date or dates. Useful if you are producing an agenda for a particular day.
  • You can exclude a date or dates from your publication. Useful if you have dates for build up and tear down in your agenda.
• Filter by Track
  • Only publish sessions in a particular track or tracks. Useful if you are producing separate agenda for separate parts of your event
  • Exclude sessions on a particular track. Can be useful to block presenting of a track until a product launch has happened.

To configure filters:

• Click ‘Publish Agenda’
• Click on the name for your existing publication
• Click ‘Configure’
• Expand the ‘Filter Speakers’ and ‘Filter Sessions’ sections and configure the filters you need
• Save and republish

How can I merge locations, tracks and roles when publishing?

When publishing you can merge content together. This enables you to publish a simpler agenda for your attendees than the one you are using to plan your event.

You can choose to merge these types of data:

• Locations. Merging location A into location B will show all sessions in location A as taking place in location B. This can be useful if you have multiple locations configured for scheduling purposes that will be experienced by the attendee as a single location.
• Tracks. Merging track A into track B will show all sessions in track A as being in track B. This can be useful if you have some tracks with only a small number of sessions and wish to present this sessions as being in a more populous track.
• Roles. Merging role A into role B will show speakers with role A has having role B. This can be useful if you have a lot of roles internally that are not intended to be shown to attendees. You can merge them into a role with a name appropriate for your attendees.

When merging the location, track, or role that you are merging into does not have to have any sessions itself. So you can use this to show a different name to attendees than you are using internally. For example you could create a ‘Main Hall’ location, and merge ‘Building B - Hall A’ into that location so attendees see ‘Main Hall’ in their agenda.

How can I embargo content that is not yet ready for the public?

You can choose to embargo session titles and descriptions if you have content that should only be shown to the public after being announced in the event.

An embargo is applied by using labels to identify the sessions that should have an embargoed session title or description.

For example if you have a label ‘New Product Launch’, you can configure an embargo to hide the session title and description from sessions with that label. Following the launch of the product you can remove the embargo and republish the agenda.

If you embargo a session or description you can replace the original text with something to indicate that the session will be published later, for example ‘Super Secret Session’.

The speakers for a session will still be shown when it is embargo’ed. To exclude a session, including it’s speakers from being published then use ‘Session Filters’ rather than an ‘Embargo Content’.

To configure an embargo:

• Click ‘Publish Agenda’
• Click on the name for your existing publication
• Click ‘Configure’
• Expand the ‘Embargo Content’ sections and configure the embargo that you need
• Save and republish

How can I publish automatically?

Still can’t find what you’re looking for? Email support@lineupninja.com and one of the team will get back to you as soon as possible.​​​​​