Quick Account Creation

Instead of being directed to a sign-up screen, users are presented with a consent page to connect to Zapier, then proceed to the Zap editor if consented. If an existing Zapier account under the email does not exist, users will receive an email prompting them to finish setting up their account. This allows users to dive directly into the Zap editor to accomplish the task at hand efficiently and without context switching.

​

Case study

Signups to use Adalo’s integration jumped 40% after embedding Zapier with Quick Account Creation into their app builder. Read more about Adalo’s user experience and results.

​

Example implementation

​

Prerequisites

• New or existing implementation of the Workflow Element, or Workflow API.
• Access to your user’s first name, last name, and email on the page supporting Quick Account Creation.

​

Add support to embed elements

You can still embed the Workflow Element or utilize the Workflow API without support for Quick Account Creation. If the four required fields aren’t provided, the embed will use the default behaviour redirecting users to Zapier’s signup page from your product’s page.

If you have an existing Workflow Element embed, you can add the new required fields for Quick Account Creation to your current code implementation, instead of re-customizing and regenerating the code. Make sure the Body code includes the below four fields with the placeholder values replaced:

clientId="your_integration_client_id"
signUpEmail="email_of_your_user@example.com"
signUpFirstName="first_name_of_your_user"
signUpLastName="last_name_of_your_user"

​

Add support to the Workflow API

​

Redirect users to the Zap editor

After an account is created with this implementation, a user token still needs to be procured to access specific Workflow API endpoints. Generally, since the user will already be signed in to their newly created account in an active session on Zapier, users won’t have to explicitly sign in again when prompted with Zapier’s OAuth flow.

https://zapier.com/webintent/create-zap
    ?template=<zap-template-id>
    &utm_source=partner
    &utm_medium=embed
    &utm_campaign=partner_api
    &utm_content=partner_quick_account_creation
    &entry-point-location=partner_embed
    &referer=<referer>
    &referrer=<referrer>
    &sign-up-first-name=<sign-up-first-name>
    &sign-up-last-name=<sign-up-last-name>
    &sign-up-email=<sign-up-email>
    &client-id=<client-id>

​

Procure a token and redirect users to a custom URL

This implementation allows a new Zapier account to be created, provides an access token to Zapier’s Workflow API, then allows you to redirect users to a custom URL of your choosing.

https://api.zapier.com/v2/authorize
    ?redirect_uri=<redirect_uri>
    &scope=<scope>
    &response_type=<response_type>
    &client_id=<client_id>
    &sign_up_first_name=<sign_up_first_name>
    &sign_up_last_name=<sign_up_last_name>
    &sign_up_email=<sign_up_email>

​

When Quick Account Creation is enabled

• If the user is already logged into Zapier, they are redirected to the Zap editor.
• If the user’s email is already associated with a Zapier account, but the user is not logged in, they are redirected to Zapier’s sign-in page.
• If the user’s email is not associated with an existing Zapier account, they are redirected to the consent page.
  • If the user consents to the terms and selects “Continue”, a Zapier account is created on their behalf and they are redirected to the Zap editor. They receive an email to finish setting up their account shortly after the account is created.
  • If the user closes the consent page, no Zapier account is created.
  • If there is an error creating an account, the user is redirected to an error page.
• In the event a user wants to sign up with a different email than the one supplied, they can edit that email within the consent page.
• In the event a user has an existing Zapier account, but it’s not under the supplied email they also have an option to sign in to any other account from the consent page.