Design Your New User Signup Flow

This implementation guide has two parts: 1) Choose your signup method 2) Diagram your post-signup workflow (optional). When you’re finished, you will know which signup method to use, and have a finished diagram for your post-signup workflow.

Part 1: Choose your method Part 2: Post-signup workflow


Summary

Chargify Feature
All signup methods
You Need
An understanding of how customers subscribe to your services, and your post-signup flow (if any).
Code
No
Difficulty
◎◎

Self-Assessment: Choose a Signup Method

In this Self-Assessment, you will review Chargify's Signup Methods, and select the best method for your business.

1. Choose your signup method

Use the information below to help you determine the best signup method(s) for your end-customer and/or your staff.

Signup Methods (7) Implementation Overview

Signup Methods
Review the signup methods below, and select your preferred method for your End-Customers, and/or for your Staff.

Method

For your

Reasons to use

PSP

End-Customer

Most common. No code, quick launch. Implementation involves linking to your Chargify-hosted Public Signup Pages (PSP). 

OSP

End-Customer

Exactly like PSP, but specifically for Offers (bundles). Offer Signup Pages (OSP).

Chargifyjs
Developers

End-Customer

Fully custom, fully in your control. Deployed on websites or web apps. For developers.

Custom
Developers

End-Customer

Fully custom, for signups that do not involve payment information. If your signup process collects payment information, use Chargifyjs. For developers.

Chargify Admin UI

Staff

Most common for Staff. No code, no implementation.

Salesforce

Staff

Your company uses Salesforce to create subscriptions.

Hubspot

Staff

Your company uses Salesforce to create subscriptions.

2. Choose your subscription structure

Determine which one(s) matter to your business. 

Subscription
Structures

Definition

Standard

Most common. A normal customer, with a normal subscription.

Grouped

1 customer who pays for multiple subscriptions, each subscription is consolidated into one invoice.

Parent/Child

A Parent Customer pays for a Child Customer’s Subscription. Uses Customer Hierarchies.

Standalone Parent

A Parent Customer, who is in a hierarchy, pays for their own Subscription. Uses Customer Hierarchies.

Standalone Child

A Child Customer, who is in a hierarchy, pays for their own Subscription. Uses Customer Hierarchies.

 

3. Review feature availability

Check if your signup method(s) choice is compatible with your subscription/customer type(s) and payment method type(s).

Subscription Structures Payment Methods
 

 

End-Customer

Staff

Structure

Customer Type

PSP

OSP

Chargifyjs

Custom

Chargify Admin UI

Salesforce

Hubspot


Standard

New              
Existing              

Grouped
New              
Existing              

Parent/Child
New              
Existing              
Standalone
Parent
New              
Existing              
Standalone
Child
New              
Existing              

 

4. Results

Based on your research in parts 1-3, get your implementation guide.

If you chose...

and your user...

Your guide is...

PSP is not logged in to your website/app when they sign up PSP Method 1: Website
Get started here
is logged in to your website/app, and is redirected to chargifypay.com when they signup PSP Method 2: Web App
Get started here
is logged in to your website/app, and stays in your app, on your domain, when they signup PSP Method 3: iFrame
Get started here
Chargifyjs is not logged in to your website/app when they sign up Chargifyjs Method 1: Website
Get started here
is logged in to your website/app, and stays in your app, on your domain, when they signup Chargifyjs Method 2: Web App
Get started here

Chargify Admin UI

is Staff

Create Subscriptions inside Chargify
Get started here

Salesforce

is Staff

Create signups in Salesforce
Get started here

Hubspot

is Staff

Currently no guide (use the Hubspot documentation instead)

Custom

n/a

Review Alternate Signup Methods

Design & Diagram: Your Post-signup Workflow

Designing your post-signup workflow is an important step, and typically one of the most difficult. You have an idea of what the end result should be, but it's difficult to determine exactly how to do it, and have it be easy to understand. To help, we're sharing a simple framework to think about your workflow, and providing clone-able LucidChart diagram templates that will walk you through the exact questions to ask when building your workflow.

1. Getting started - understand the workflow framework

Workflows can be complex, but this framework will help you simplify. There are 3 parts to the workflow:

Workflow Section Description
1. Trigger How the workflow begins. Typically a Chargify webhook (or perhaps real-time if you're using Chargifyjs).
2. Data Determining the data you need, finding where it exists within Chargify data.
3. Action(s) Now that you have all of the data, you apply optional filters (eg: if subscription is active), and then you perform the action that matters. There are 2 types of actions:

1. Chargify Action - making an API call to Chargify, such as updating a subscription.
2. Database Action - making a database request in your system, such as updating a user's subscription status to active

Chargify Action Database Action Both
Begin at the green Start Workflow, and read through the diagram.

Chargify_Action.png
2. Get a diagram template  Lucidchart

Each template is powered by LucidChart, an industry leader in diagramming software. You may have an account already, but if you don't, just click on a template below and LucidChart will prompt you to create a free trial. From there, clone the template into your account, by clicking File > Duplicate.

Template Design a workflow that... Example Get Template*
Free LucidChart account required
Chargify Action Makes a Chargify API Action in Chargify. When a subscription is created, update the next billing date. Open in Lucidchart
Database Action Talks to your database. When a subscription is created, set the user as active in your database. Open in Lucidchart
Chargify Action & Database Action Makes a Chargify API Action in Chargify and talks to your database. When a subscription is created, update the next billing date, and set the user as active in your database. Open in Lucidchart
3. Create your diagram

Section 1: Trigger
The trigger represents how the workflow begins. With post-signup workflows, it is always the signup_success webhook. If you are using Chargifyjs, there are times when you want a real-time workflow, such as making the user active in your database. In your diagram, simply replace the webhook trigger with a "Real-time" trigger for the submission of your Chargifyjs form.

flow-1.png

Section 2: Data
Spend some time determining all of the data you need to make your workflow come to life. You can view the signup_success payload here to determine where specific data points are located.

flow-2.png


If there are any remaining data points not in the webhook, an API call needs to be added to fetch the data. A common example is getting the number of user seats.

flow-3.png

Section 3: Action(s)
There are 2 actions in post-signup workflows: a Chargify Action (an API request to Chargify to create/update a record), a Database Action (to update your web application).

If you are doing a Chargify Action, such as updating the next billing date, your diagram might look like this:

flow-4.png

If you are doing a Database Action, such as setting a user's status to active, your diagram might look like this:

flow-5.png

4. Determine how you will implement the workflow

There are 3 implementation methods for any type of workflow.

Method Select if... Example
No Code You already know the system that will power the workflow for you, or you hire a developer. You hire a developer.
Low Code You already know the system that will power the workflow for you, and some small code is required. Zapier
Custom Code
Most common
Developers
You, or your team, are developers who plan on writing custom code to build the workflow. You build an endpoint in your app that accepts Chargify webhooks and executes the workflow.
5. Start building

You're ready to get started. [Examples of builds coming soon]


Diagram Template Collection

Workflow Get Template*
Free LucidChart account required
On signup, update user seats in database Open in Lucidchart
On signup, update a user status to active in database Open in Lucidchart
On signup, create user in database, with many fields (subscription ID, plan name, etc) Open in Lucidchart

FAQs

  1. Can Chargify help me build my workflow?
    No. Chargify is a Product-focused company, rather than Custom-service-focused.

  2. Can Chargify help me determine which API endpoints and webhooks to use?
    Yes, depending on your Chargify Onboarding Plan. Ask your Implementation Consultant.

  3. What if I want to create subscription in another system?
    If you have the development experience, Chargify has the APIs to help. First, make sure the other system has the webhook(s) you need. If yes, set up an endpoint in your application that listens for that webhook, and use Chargify's create subscription API to create the subscription in Chargify.
Was this article helpful?
1 out of 1 found this helpful