Create a Newsletter List With

In this video, we are going to create a Flow that will add a user to a newsletter list if they opt in for it.
This Flow is going to have two operations, the first operation will check if the user chooses to opt into our newsletter, and then if they did we are going to create another operation that will add that user to the "Newsletter list" collection. Easy peasy.
You can support my work on Patreon
/ watchlearn
Follow me on Social Media
Github: github.com/ivandoric
Twitter: / ivan_doric

Пікірлер: 5

  • @RobertWildling
    @RobertWildling11 ай бұрын

    My recommendation in August 2023: set the default value of the newsletter toggle to false, otherwise the flow will not pick up on it and cause an error.

  • @user-iy9eu6uh7z
    @user-iy9eu6uh7z7 ай бұрын

    This flow works seamlessly for my use case when creating a client. However, I'm encountering challenges when attempting to update a client's profile, as the payload is returning as 'undefined,' preventing the successful addition of the client to the list. Seeking assistance to resolve this specific issue during profile updates.

  • @harrishpaul7374
    @harrishpaul737411 ай бұрын

    Bro how to update the field using flows in event hook

  • @MattexFilms2006
    @MattexFilms2006 Жыл бұрын

    I followed this tutorial in Directus v9.22.3 and the flow doesn't want to work. The flow runs when a user is created, though the only fields that are passed in the trigger payload are the first_name, last_name and email. The newsletter field, even though it was set to enabled wasn't passed at all. The payload of the "Check newsletter opt-in" condition has a details.message of ""$trigger.payload.newsletter" is required"

  • @RobertWildling

    @RobertWildling

    11 ай бұрын

    I had the same problem. It seems that only fields that have been changed are sent to the flow's payload. When you set the newsletter toggle's default value to false, then you can toggle it to true when creating a new user - and this should be picked up by the flow. Not sure since when this is the standard behaviour of Directus flows... maybe it is even a bug.