Payment Completed (Gravity Forms) → Create User

Use Case

When a payment is completed through Gravity Forms, you want to automatically create a WordPress user account. This bridges form-based sales with site access.

Common scenarios:

• Course enrollment creates student account
• Service purchase creates client portal access
• Event registration creates attendee account
• Membership sold via form
• Consultation creates customer account

Step-by-Step Setup

1. Prerequisites

Ensure you have:

• Gravity Forms with payment add-on
• Form with email and name fields
• Payment processing configured

2. Create a New Workflow

Navigate to Sequensy → Workflows in your WordPress admin and click Add New Workflow.

Name your workflow “Create Account on GF Payment” or “Course Student Registration”.

3. Configure the Trigger

Select Payment Completed (GF) as your trigger.

Available filters:

• Form: Specific enrollment/purchase forms
• Payment Amount: Minimum payment threshold
• Products: Specific GF products that require accounts

4. Set Up the Create User Action

Configure the user creation:

5. Send Access Email

Chain a Send Email action:

Subject: Your account is ready!

Hi {first_name},

Your payment has been processed and your account is ready!

Login Details:
URL: {login_url}
Username: {email}
Password: Set using the link below

Set Your Password: {password_reset_link}

Once logged in, you'll have access to:
- Your dashboard
- {purchased_content}
- Support resources

Questions? Reply to this email.

Welcome aboard!

6. Test Your Workflow

1. Enable the workflow
2. Submit form with payment
3. Complete payment process
4. Verify account was created
5. Test login with new account

Pro Tips

Check for existing accounts: Add a condition to skip if email already has an account—link order instead.

Map all fields: Capture phone, company, and other form fields as user meta.

Immediate access: Users expect instant access after payment—ensure account creation is fast.

Clear instructions: Tell them exactly how to access what they paid for.

Form Field to User Mapping

Account Templates by Use Case

Online Course

Role: Student
Access: Course content
Meta: enrolled_courses, enrollment_date
Email: Welcome + first lesson

Service Client

Role: Client
Access: Client portal
Meta: service_purchased, service_start_date
Email: Welcome + booking link

Event Attendee

Role: Attendee
Access: Event area
Meta: event_registered, ticket_type
Email: Confirmation + event details

Membership

Role: Member
Access: Member content
Meta: membership_level, join_date
Email: Welcome + getting started guide

Workflow Sequence

1. Form submitted with payment
         ↓
2. Payment processed (GF)
         ↓
3. Payment Complete trigger fires
         ↓
4. Check if account exists
   ├─ Yes: Update existing user meta
   └─ No: Create new account
         ↓
5. Assign appropriate role
         ↓
6. Store purchase metadata
         ↓
7. Send welcome email
         ↓
8. User has immediate access

Handling Existing Accounts

Strategy 1: Update Existing

Condition: Account with {email} exists
Action: Update user meta instead
Add: purchased_product to their account
Skip: Account creation
Notify: "Additional access added"

Strategy 2: Link and Inform

Condition: Account exists
Action: Link entry to existing user
Action: Send email about new access
Skip: Account creation
Message: "New purchase added to your account"

Troubleshooting

Account not created?

• Verify payment completed (not just submitted)
• Check email field mapping
• Review form submission

Duplicate account error?

• Add condition for existing accounts
• Check email uniqueness
• Review workflow conditions

User can’t log in?

• Verify password reset email sent
• Check email delivery
• Confirm account is active