Hi Chris,
It seems that custom tile could meet your requirement.
In addition to documentation instruction, please refer to my personal summary of the custom channel feature:
1. Create a custom entity, it is used to store and display information about our custom channel.
e.g: The entity would have an optionset field to store different social media platforms: record 1 is for Facebook, record 2 is for Twitter.
2. Follow the documentation or these two community blogs to configure custom tile.
https://community.dynamics.com/365/marketing/b/dynamics-365-for-marketing-community-blogs/posts/custom-touch-point-custom-tile-in-customer-journey-in-less-than-10-minutes
https://community.dynamics.com/365/marketing/b/dynamics-365-for-marketing-community-blogs/posts/firetext-sms-
3. After configuration done, if we want to generate twitter post, then set record 2 to dropdown menu of the custom tile.
4. In live CJ, when contact goes to the custom tile, an entity record called "Custom Channel Activity" will be created, it contains regarding contact and custom entity record.
Therefore, we can trigger workflow/flow(recommended) on creation of the entity and do further actions.
e.g:
When a custom channel activity is created
↓
Retrieve custom entity record based of data of the new custom channel activity
↓
If optionset field of the record is set to "Twitter", connect to Twitter using Twitter connector and generate Twitter activities.
5. Data that how many contacts are processed will also display at top of the custom tile like other OOB tiles.
I built a solution including custom tile before, you could import it to sandbox environment to test.
[View:/cfs-file/__key/communityserver-discussions-components-files/768/7713.CustomChannelExtendModule_5F00_1_5F00_0_5F00_0_5F00_1.zip]
My custom entity is called "Twitter Channel"(Its display name in CJ is twitter message.), so what you only need to do are:
1. Add the entity to sitemap of your marketing app and create a new record.
2. Create a flow on creation of Custom Channel Activity and connect to social media using connectors.
3. Run a CJ to test.
