Username already exists

Hi ​@leidagroot 

Try reaching out to LearnDash Support for help with their Zap app integration that they created and manage using the Zapier Developer Platform.

For us to have more info, post screenshots showing how your Zap steps are outlined and configured, along with the encountered error.

Thanks for your answer!

Here are some screenshots. 

Hi ​@leidagroot 

First, you are using a deprecated Zap trigger event, so that needs to be updated.

Click the Username field to see the tooltip that may have more info about expected values/formats.

Check to make sure you are using the correct version of the LearnDash Zap app integration as there appears to be an updated logo.

Hey ​@leidagroot 👋 Did Troy's suggestions help to get rid of that "User could not be created" error?

Want to make sure this gets sorted, so keep us posted on how it's going! 🙂

This needs a “find-or-create, then enroll” flow rather than calling Create User unconditionally.

I’d structure it as:

1. Normalize the purchaser’s email/username.
2. Look up the existing WordPress/LearnDash user first.
3. If found, pass that existing user ID directly to the course-enrollment action.
4. Only if not found, create the user, capture the returned user ID, then enroll.
5. Use the Plug&Pay order/transaction ID as an idempotency key so a retry cannot enroll or create twice.

If the current LearnDash Zap app does not expose “Find User” or “Enroll Existing User,” the safe fallback is a WordPress/LearnDash API request that resolves the user first—never generate a second username just to get past the error.

We had the same identity-resolution problem while building Atlantic’s CRM automations. Separating contact resolution from the downstream action removed both duplicate records and retry races.

I’m Ege, co-founder of Atlantic, sharing our implementation pattern—not representing LearnDash or Zapier.

Hi ​@leidagroot just checking — did any of these fixes do the trick for you?