This application leverages the power of third-party OAuth providers, allowing users to build email lists from returned OAuth data, and seamlessly integrates with various email service providers.
- Create and manage email lists
- Generate campaign links for easy subscriber sign-up flow
- Integrate with Google and Discord OAuth Providers, with more coming soon
- Redirect users to a specified URL after subscription
- Post subscriber data to third-party applications on sign-up (currently supports output to Aweber, Brevo, Resend, and Telegram)
The application is essentially an opt-in funnel.
Traffic enters the funnel at the Campaign URL, is taken to the Application, and then redirected to the specified OAuth Provider (Google, Discord, etc). At this point the visitor has the option to authorize the Application. If they agree, they are redirected back to the Application, and then out to the final URL.
In addition, a callback is triggered containing the subscriber info (email address, name, etc). This info is saved to the database, and (optionally) sent to any 3rd-party Outputs specified in the Campaign.
-------> (8) Subscriber info is sent to 3rd-party output(s) (optional)
|
| ______
| | |
|-------> | DB | (7) Subscriber info is saved to DB
| |______|
_________|
| | ------> (6) Visitor is redirected to final URL
(1) Visitor clicks on Campaign URL ---> | App |
|_________| <-------------------------------------------
| ^ |
(2) Visitor is redirected to OAuth Provider | | |
| | (5) Visitor is redirected back to App |
⌄ | |
__________ |
| | |
| OAuth | |
| Provider | -------------------------------------------
| (Google) | (4) Subscriber info is sent to App via callback
|__________|
(3) Visitor authorizes App
To get the project running locally make sure you have Go and Docker installed, then follow these steps:
- Clone the repository:
git clone https://github.com/EricFrancis12/oauth-email-lists.git- Enter project directory:
cd oauth-email-lists- Install dependencies:
go mod download- Run the following command to create a boilerplate
.envfile at the project root:
make create-env- Spin up a local Postgres instance:
docker compose up -d- Run the application:
make runThe application should now be running at http://localhost:6009 by default.
The Root User has the ability to create new users. Log in as the root user by visiting /login, and entering the ROOT_USERNAME and ROOT_PASSWORD from the .env file into the form.
Then, create a new user by sending a POST request to /users:
curl -X POST "http://localhost:6009/users" \
-H "Content-Type: application/json" \
-d '{
"name": "Jim Bob",
"password": "abcdefgh"
}'To verify the User was created successfully, make a GET request to /users. The response should include the newly-created User:
{
"success": true,
"data": [
{
"id": "sdq0e64g-5lq2-467m-9xs6-s0fp4945xlgf",
"name": "Jim Bob",
"hashedPassword": "$2a$10$k4r2SwdJWa62ql/s4J4qcpcbVqt5o.JEBqWpUAgDPFIU/6cJP.iu8i",
"createdAt": "2024-08-22T20:26:06.874752Z",
"updatedAt": "2024-08-22T20:26:06.874752Z"
}
]
}A User may have many Email Lists associated with them. To create a new Email List, make a POST request to /email-lists, making sure to reference the User ID that it should be attached to.
curl -X POST "http://localhost:6009/email-lists" \
-H "Content-Type: application/json" \
-d '{
"name": "My First Email List",
"userId": "sdq0e64g-5lq2-467m-9xs6-s0fp4945xlgf"
}'Verify the Email List was created successfully by making a GET request to /email-lists. You should see the newly-created Email List:
{
"success": true,
"data": [
{
"id": "9ealnr84-lap9-4194-sko9-7a2aq4571nr6",
"userId": "sdq0e64g-5lq2-467m-9xs6-s0fp4945xlgf",
"name": "My First Email List",
"createdAt": "2024-08-22T20:27:21.874752Z",
"updatedAt": "2024-08-22T20:27:21.874752Z"
}
]
}Outputs are third-party applications that can be interacted with when a new subscriber is added to an Email List. More outputs will be added soon. Currently supported outputs include:
To integrate with AWeber, simply sign up for an account at https://aweber.com, and create an email list. Then navigate to List Options -> List Settings and get your List ID (see image below).
Now make a POST request to /outputs:
curl -X POST "http://localhost:6009/outputs" \
-H "Content-Type: application/json" \
-d '{
"userId": "sdq0e64g-5lq2-467m-9xs6-s0fp4945xlgf",
"outputName": "aweber",
"listId": "awlist8157462",
"param1": "[optional AWeber ad tracking]"
}'To integrate with Brevo, sign up at https://brevo.com. Navigate to Contacts -> Lists in the Brevo dashboard (see image below).
Brevo uses numeric list IDs unique to each account, so the List ID that we want is 2.
Next, go to https://app.brevo.com/settings/keys/api and create a new API Key. Then add your API Key to the .env file for BREVO_API_KEY.
Now we can make a POST request to create a new Brevo Output:
curl -X POST "http://localhost:6009/outputs" \
-H "Content-Type: application/json" \
-d '{
"userId": "sdq0e64g-5lq2-467m-9xs6-s0fp4945xlgf",
"outputName": "brevo",
"listId": "2",
"param1": "[optional EXT_ID Contact Attribute ]"
}'To integrate with Resend, sign up at https://resend.com.
Resend uses an Audience ID to uniquely identify Audiences on their platform. Navigate to the Audiences tab on their dashboard, and create a new Audience if needed, and grab your Audience ID (see image below).
Next, go to the API Keys tab and create a new API Key. Then add your API Key to the .env file for RESEND_API_KEY.
Finally, make a POST request to /outputs to create a new Resend Output:
curl -X POST "http://localhost:6009/outputs" \
-H "Content-Type: application/json" \
-d '{
"userId": "sdq0e64g-5lq2-467m-9xs6-s0fp4945xlgf",
"outputName": "resend",
"listId": "e0a3e864-da54-49"
}'To integrate with Telegram, you will need to obtain a Telegram Bot ID, as well as the Chat ID of where the messages should be sent.
This video explains how to create a Telegram Bot and get the Bot ID: https://www.youtube.com/watch?v=Qe16589RNNY
This video explains how to get your Telegram Chat ID: https://www.youtube.com/watch?v=uXhFsScozyY
Add your Bot ID to the .env file for TELEGRAM_BOT_ID.
Now you need to define the message content. You can substitute in values for subscriber.name and subscriber.emailAddr by using {{name}} and {{emailAddr}} respectively. For example, if this is the message content:
"A new subscriber was just added. Their name is {{name}}, and their email address is {{emailAddr}}."
And a new subscriber named Tom Jones, with an email address of [email protected] subscribes, the message will be evaluated to:
"A new subscriber was just added. Their name is Tom Jones, and their email address is [email protected]."
Now we can make a POST request to /outputs to create a new Telegram Output:
curl -X POST "http://localhost:6009/outputs" \
-H "Content-Type: application/json" \
-d '{
"userId": "sdq0e64g-5lq2-467m-9xs6-s0fp4945xlgf",
"outputName": "telegram",
"listId": "[your-chat-id]",
"param1": "[your-message-content]"
}'Users must specify an OAuth Provider when creating a campaign. More providers will be added soon. Currently supported providers include:
- Discord
To integrate with Google as an OAuth Provider, visit https://console.cloud.google.com and create a new project. Then navigate to https://console.cloud.google.com/apis/credentials and create your credentials. After that you will have an Client ID and Client Secret for your project.
Now add your Client ID and Client Secret to the .env file for GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET respectively.
Also, you will need to set Authorized JavaScript origins and Authorized redirect URIs in your console for wherever you plan to run the app (see image below).
To integrate with Discord as an OAuth Provider, create a Discord developer account if you don't already have one, then navigate to https://discord.com/developers/applications and create a new application.
Grab your Client ID and Client Secret, and add them to the .env file for DISCORD_CLIENT_ID and DISCORD_CLIENT_SECRET respectively.
Also, you will need to add Redirects in your dashboard for wherever you plan to run the app (see image below).
Any User may create a Campaign by making a POST request to the /c endpoint:
curl -X POST "http://localhost:6009/c" \
-H "Content-Type: application/json" \
-d '{
"emailListId": "9ealnr84-lap9-4194-sko9-7a2aq4571nr6",
"providerName": "Google",
"outputIds": [
"[your-first-output-id]",
"[your-second-output-id]"
],
"redirectUrl": "https://bing.com?src=my-redirect-url"
}'Response:
{
"success": true,
"data": "http://localhost:6009/c?c=eyJhbGciOiJIUzI1NJ9.eyJkExLWIwNTktiIsIsnR5cCI6IkpXVCNTik2YTgUzNGFkiYi1JVxMDAyiNiVcVcdTAwMjYvlXHUw0ElMkYlMkwr5wnLmNvTAwMjYlX4ZyKKbSgUzRnNyYyUzRG15LXJlZGlyZWNYeXRhIjoiMWhjduN1MDAyNiVcdTAwMjYlXMDI2JVx1MDAyNiZhZGQxZDEtZxGVmOC00ZD0LXVybCJ9.PyCc0f"
}This is the Campaign URL you would use as the entry-point to the funnel.