Schedule API on a list from Input

Need help APIs
1

Hey,

Has anyone every experienced running a Schedule API on a list using an dynamic single line input?

Currently I am using the Tagger Plugin to @mention people from my user DB, when a comment is made with these people I store it in my comments DB.

Note multiple people can be @mentioned in one comment, & I would like to create a line item in the comment DB for each user @mentioned in the comment (if even the messages are duplicate).

However, when I have set this up, I can only Schedule my API on a list from an existing DB & not from the input value.

Does anyone have a possible solution to this?

2

So the comment (after created) is the trigger, right? And the input generates a list of mentions.

What you are trying to do right now? Can you share some screenshots?

3

Hey!

Correct, there is a submit button which triggers this.

You can see the work idea here, you can see I have two people from my DB who are with a message

I have a second input which remains hidden (only showing it now so you can see) which extracts the names & has them as a comma separated value.

However I can’t seem to run this input’s data as a list, rather it added boths names in one line item in the comment DB

image
image862×602 37.9 KB

4

To expand further, I am not married to having this as seperate line items, but rather when I display stats, I would like to have a count per @mention, where currently it shows @mentionOne & @mentionTwo as a separate line item as as having only @mentionOne

Here is an example:

image

5

Well, as I’ve never used this plugin I don’t know how it really works. However, I think what’s missing here is that you need to split (using a comma as delimiter) the value that stores all the mentions separated by a comma.

This way you will be generating a list. These will probably be a list of text values ​​so to define the [thing] to be changed, you will need to use a search and use a constraint with the text (the mention) extracted.

But if in the hidden input you can extract the user and keep them as users, then you just need to pass all the them as the source (a list of users) to the Backend Workflow.

Maybe you don’t even need the hidden input, just need to use the same logic you are using to extract with the split piece and pass it directly to the Backend Workflow or maybe store them in a Custom State.

6

Hey!

I was able to figure it out by creating a master tracking DB & then a subsidiary DB specific to @handle tagging & then using recursive workflows to split it