Pokémon of the Day, Part 2

Assuming you have already completed Part 1 of this Tutorial, you can now expand your Pokémon of the day Integration by adding dynamic configurations with options populated by an init sync flow.

The students at the Pokémon Trainer Academy love using your integration so much that they've requested new features! Instead of having all the students receive the same Pokémon message, each student wants the ability to choose which type of Pokémon they will learn about.

Here is how you will accomplish this:

• Each Pokémon trainer will have their own integration tenant, and they will tell the Academy's integration user experience administrator their preferred connection settings.
• For each tenant the Academy's UX admin will be able to select one Pokémon trainer as the recipient for the daily Slack Message: the integration will dynamically populate those options by reading available users from the Slack workspace.
• For each tenant the Academy's UX admin will be able to select one Pokémon type -the one chosen by the tenant's trainer: the integration will dynamically populate those options by reading the different Pokémon types from the PokéAPI, ensuring the list remains updated even with new additions.

Here's what you will get to do along the way:

• Add an init sync flow.
• Add dynamic configurations.
• Make new releases for this integration.

You should already have the following from Part 1 of this Tutorial:

• A Pokémon of the Day Slack App that provided the client ID and client secret for your Slack connector.
• A Pokémon of the Day integration on your Pandium sandbox integration hub.
• A connected tenant for that integration which created a Slack Bot User OAuth Token to use in your .env during local development.

These will all be used as you build these new features, so you can dive right into writing the code!