Skip to content
API to receive contact me message to your email or mobile
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


  • This module helps the "contact me" page to process the requests using nodejs or aws lambda functions.

Preview (DEVEL)

Portfolio Preview1


Portfolio Preview1

View Live Preview using "Contact Page"


GitHub license

Download and Installation

To begin using this module, choose one of the following options to get started:

  • Clone the repo: git clone
  • Install grunt (if you don't have it installed) npm i -g grunt
  • Install project dependencies npm i

Basic Usage

After download and install:

  • Edit or cretae a js file /v1/{your_endpoint}/{your_endpoint}.js.
  • Edit or cretae a js file /classes/{your_class}.js.
  • Create the file private_config.json with your own twilio, gmail and AWS settings. You can use _private_config.json as a base example.
  • Run the project grunt
  • Open your web browser: localhost:5800

Test Parameters


    "name": "Albert Roberts",
    "phone": "5591112233",
    "email": "",
    "message": "Testing SMS and email"

Calling http://localhost:5800/{your_endpoint} using GET or POST (Same parameter names that DEVEL)

Configuration Settings

  • The file private_config.json will contain all the API Keys, credentials, production params that supports the implementation.
  • This file will be ignored on the repository.
    "TWILIO": {
        "NUMBER": "+15591112222",
    "GMAIL": {
        "USER": "",
        "PASS": "YOUR_PASSWORD",
        "CC": "optional emails separates by `,`"
        "swagger": "2.0",
        "region": "us-west-2",
        "account": "aws_acc_number",
        "lambda": "lambda_name",
        "lambda_version": false,
        "lambda_runtime": "nodejs8.10",
        "lambda_role": "arn:aws:iam::[account]:role/[awsrole]",
        "lambda_handler_name": "handler",
        "lambda_timeout_sec": "10",
        "version": "default",
        "base_path": "default",
        "schemes": ["http", "https"],
        "swagger_host": "http://localhost:5800/swagger/",
        "deploy_cmds": {
            "cmd_custom_copy_dirs": [],
            "cmd_custom_copy_files": [""]

Note: You can also protect your deploy by overwriting your production settings on production enviroment. See Advanced Usage

Deploy to production using AWS

Elasticbeanstalk Deploy:
  • Install The Elastic Beanstalk Command Line Interface (EB CLI)[^ebcli]
  • eb init
  • eb create [ENV_NAME]
  • eb setenv DEV_ENV=production
    • Or all at once: eb setenv DEV_ENV=production TWILIO_NUMBER=+1112223333 ... [all your config features]
    • See _private_config.json and config.js
  • eb use [ENV_NAME]
    • Remember to always commit your changes before eb deploy
  • eb deploy or eb deploy [ENV_NAME] See more info about EB CLI here
Lambda - GATEWAY Deploy:
  • Be sure all your references on the Configuration file are matching your aws settings (APIGATEWAY settings).
  • Edit apigateway.swagger.config.json
    "host": "",
    "resources": [{
        "path": "/",
        "requestTemplate": {}
    }, {
        "path": "/contactme",
        "requestTemplate": {
            "_operation": "portfolio/portfolio",
            "action": {
                "required": true,
                "type": "string",
                "description": "Do not change the value",
                "default": "testapi"
            "name": {
                "type": "string",
                "required": true,
                "description": "Name of the person is contacting."
            "phone": {
                "type": "string",
                "required": true,
                "description": "Phone of the person is contacting."
            "email": {
                "type": "string",
                "required": true,
                "description": "Email of the person is contacting."
            "message": {
                "type": "string",
                "required": true,
                "description": "Message to send."
  • Parameter details:

    • host: AWS REST BASE URL
    • resources {Array of Resources} : API endpoints layout definition
      • path : Public api endpoint path when it is deployed.
      • requestTemplate : Parameters to use in lambda function.
      • _operation : Link to the endpoint source name.
      • action,name,phone,email and messsage ...: Custom parameters according your implementation.
  • Run grunt build-api --deploy-all.

    If everithing is OK you will be able to see your API on aws:

Portfolio Preview1

Advanced Usage


After download and install, simply edit or cretae a json file /v1/{your_endpoint}/_test.json to perform your test.

/*  You can use comments in this JSON file */
    "delay_ms": 1000,
    "tests": [{
        // Add custom flags to use in lib/server-utils.js: performTest(t)
        // "enabled": false,
        "event": {
            "mode": "keepalive",
            "action": "testapi",
            "name": "Albert Roberts",
            "phone": "5591112233",
            "email": "",
            "message": "Testing SMS and email"
    }, {
        "enabled": true,
        "event": {
            "mode": "keepalive",
            "action": "testapi",
            "name": "Mario Stone",
            "phone": "3334445555",
            "email": "",
            "message": "Testing SMS and email"

Running Example: Portfolio Preview1

OVERWRITE Production Settings:

The config.js file can be modified:

if (ENV.environment === 'production') {
        // Overwrite settings

        ENV.GMAIL.USER = process.env.GMAIL_USER || ENV.GMAIL.USER;
        ENV.GMAIL.PASS = process.env.GMAIL_PASS || ENV.GMAIL.PASS;
        ENV.GMAIL.CC = process.env.GMAIL_CC || ENV.GMAIL.CC;

Remember to set DEV_ENV=Production and the custom Environment Variables as AWS Elasticbeanstalk Deploy indicates.

Important Note: **This functionality only applies for Elasticbeanstalk.

Grunt Tasks

  • grunt the default task that builds everything
  • grunt build-api generates all dependencies to deploy in a Serverless[^serverless] Approach using AWS Lambda - API Gateway [^awslambda]
    • --deploy will deploy the endpoints to the REST GATEWAY only.
    • --deploy-all will deploy the endpoints, lambda function and will setup the execution rights.
  • grunt remove-api deletes the deployed resources in AWS.
    • --api will delete the REST GATEWAY only.
    • --all will delete all on AWS regarding the API deploy.

Custom Classes


  • sendsms (params)
params: Object
    mobile: string 


  • send (params)
params: Object
    from: string | config.USER,
    to: string,
    cc: string |,
    subject: string,
    body: string | 'hello world!'


Setup your own firebase settings on private_config.json


  • isExistingApp (name) -- returns boolean
  • generateToken(name, uid, data) -- returns promise
  • listen (path, on_event, callback) -- returns promise
  • read (path) -- returns promise
  • update (path, snapshot) -- returns promise
  • write (path, snapshot) -- returns promise
  • push (path, snapshot) -- returns promise
  • remove (path) -- returns promise
  • findBy (path, key, value, bypass) -- returns promise

Bugs and Issues

Have a bug or an issue with this template? Open a new issue here on GitHub.

Custom Builds

You can hire Paulo to create a custom build of any template, or create something from scratch. For more information, visit my freelancer page.


API is an open source repository released under the MIT license, which means you can use them for any purpose, even for commercial projects.

API was created by and is maintained by Paulo C Ruvalcaba.

Copyright and License

Copyright 2013-2018. Code released under the MIT license.


You can’t perform that action at this time.