Build web application, connected to 1 API + web scraping job
Budget: $250 – $750 USD
I need a simple web application to be created on top of 1 API + there's some web scraping / automation to be done as well. Features of the web app are pretty basic (create an account, pick a plan using Stripe, etc.) and Django / Node boilerplate is available.
Besides that, users would need to be able to add their inboxes using Oauth (ideally), for which we could use Pathfix so we don't have to use Google API directly.
Then there's some browser automation / scraping needed on which I can go into more detail in chat.
Main workflow for users
User creates an account
User upgrades to a plan (or already purchased a plan earlier)
User adds 1 or several email inboxes to the application using Oauth
User sets an interval to run tests (daily, weekly, monthly)
User closes the tab
We run daily, weekly, or monthly tests for each inbox the user has connected (anywhere between 1-100 inboxes usually)
Test workflow step #1: use the mail-tester.com API (below) to send an email from user their inbox and see if inbox is blacklisted or not and to check SPF,DKIM,DMARc settings
Test workflow step #2: use the gmass.co/inbox option to send an email from user their inbox and see if emails are landing in primary or spam
Test workflow step #3: store the results and display them in a report in the web application
Test workflow step 4: send a report to the user to show overall health of all of his inboxes
Nice to have: send the report to a webhook too, so user can use Zapier to receive reports in Slack
Examples of similar apps:
https://folderly.com/
Boilerplate we can use:
https://rocketapp.me/
https://serverless.page/
API’s you’ll use:
https://www.mail-tester.com/manager/api-documentation.html
Pathfix.com for Oauth of Gmail, Zoho, Outlook
Website we need some scraping / automation on:
gmass.co/inbox
Automation here is simple. We send an email on set intervals from inboxes a user connected to the list of emails in the website above (it’s a fixed list so we can just store that on our end), then later run a query for gmass.co/inbox?q=user%40website.com, then grab some CSS/HTML selectors from the page to see if the email landed in “primary inbox”, “spam”, or somewhereelse. The results we then need to store / display on our end.
Besides that, users would need to be able to add their inboxes using Oauth (ideally), for which we could use Pathfix so we don't have to use Google API directly.
Then there's some browser automation / scraping needed on which I can go into more detail in chat.
Main workflow for users
User creates an account
User upgrades to a plan (or already purchased a plan earlier)
User adds 1 or several email inboxes to the application using Oauth
User sets an interval to run tests (daily, weekly, monthly)
User closes the tab
We run daily, weekly, or monthly tests for each inbox the user has connected (anywhere between 1-100 inboxes usually)
Test workflow step #1: use the mail-tester.com API (below) to send an email from user their inbox and see if inbox is blacklisted or not and to check SPF,DKIM,DMARc settings
Test workflow step #2: use the gmass.co/inbox option to send an email from user their inbox and see if emails are landing in primary or spam
Test workflow step #3: store the results and display them in a report in the web application
Test workflow step 4: send a report to the user to show overall health of all of his inboxes
Nice to have: send the report to a webhook too, so user can use Zapier to receive reports in Slack
Examples of similar apps:
https://folderly.com/
Boilerplate we can use:
https://rocketapp.me/
https://serverless.page/
API’s you’ll use:
https://www.mail-tester.com/manager/api-documentation.html
Pathfix.com for Oauth of Gmail, Zoho, Outlook
Website we need some scraping / automation on:
gmass.co/inbox
Automation here is simple. We send an email on set intervals from inboxes a user connected to the list of emails in the website above (it’s a fixed list so we can just store that on our end), then later run a query for gmass.co/inbox?q=user%40website.com, then grab some CSS/HTML selectors from the page to see if the email landed in “primary inbox”, “spam”, or somewhereelse. The results we then need to store / display on our end.