Send email to user startet by zapier

Hi everyone, I want Zapier to transfer user data from Digistore24 to Bubble using the “Create a new thing” function. It’s already working perfectly; the test was OK.

Now Bubble is supposed to send a “Reset Password Email” to this email address. Unfortunately, I don’t understand how to set up the workflow.

Can someone help me? That would be great :slight_smile:

What I tried:

I created a backend workflow. I selected the following condition:

Step 1: “Data type” before change’s email is not “Data type” now’s email
Step 2: Send password reset email

Unfortunately, no email was sent.

Am I on the right track?

You can only apply the Reset password email action to an existent registered user. Which user are you trying to reset the password? What does it have to do with the Create a new thing action?

Hi,

I think it’s best to summarize what I need (I hope I describe it correctly, I’m still new to Bubble):

I need a workflow that should be triggered by a new record (last name, first name, email address, name of the purchased product on Digistore24).

The new record is created by Zapier when a purchase is made on Digistore24.

In order for the new user to be able to log in to Bubble, I need a workflow that send a “password reset email” to the newly created email address of the record (I assume these are the correct process steps).

This is the required process that I want to map in Bubble.

Setting an email value in a field of a random datatype does not register a new user by itself. You first need to register the user.

Check this action How to Create an Account For Someone Else | Bubble

Okay, now I get it :blush: (I hope so)

Then the process should look like this:

  1. Zapier creates a new record, including an email address unknown to the system.
  2. If I understand correctly, I now have to instruct the system to send a “How to Create an Account For Someone Else” email to this new email address, right?

However, I still have the question of how the workflow is triggered. I’ve seen various approaches in the form, but I don’t really understand which one would be suitable for me.

For example, would that be “USER before change’s email is not USER now’s email?”

You’ll need to execute a Create an account for someone else action. I guess you’ll want to do that as soon as the record is created, unless you have already created an user for that email address.

Additionally you might want to exeute additional actions such as linking that newly created record to the user.

Can’t recall if the password setting is part of the action itself. I belive it is

I think we both agree.

What I don’t understand: How to set the parameters.

So far, I’ve assumed I’m starting with a backend workflow. But which one? I’m new to bubble, and I don’t really understand the logic behind the parameters that need to be entered for “Only when.”

As part of this workflow that you stated is in place and working perfectly at the moment

This is the result of the Zap when a purchase was made via Digistore24.

In the next step, I tried to start the bakend workflow. Unfortunately, I only have these two options, and I don’t understand the logic behind them. Could you tell me how I should combine these two parameters?

I tried this version, but I couldn’t get any further in the next step either.

I just can’t get any further here

Is this even the right approach?

I guess you have an API Workflow already in place that is creating the Kunden record isn’t it?

The Kunden record is created via the API by Zapier

Here are my data types for better representation

If I understand correctly, I need to create a bubble user from the data that Zapier creates in the Kunden data type. Is that correct?

That’s correct.

You have two options:

  1. New zap step + new API workflow
    • As part of your zap, adding a new step that calls a new API Workflow Create user, sending the email.
    • The Create User API workflow
      • receives the email
      • creates the User with the Create an account for someone else action
      • Adds existing Kundenrecords to it
  2. Use a Database trigger event
    • that monitors Kunden object creation
    • creates the User with the Create an account for someone else action, with email stored in the monitored Kunden record, only if an account doesn’t exists already
    • Adds monitored Kundenrecord to it

This topic was automatically closed after 70 days. New replies are no longer allowed.