Una lib simple para enviar emails usando la API de Gmail con autenticación de Service Account.
- ✅ Envío de emails usando Gmail API
- ✅ Soporte para Domain-Wide Delegation
- ✅ Manejo robusto de errores
- ✅ Validación de formatos de email
const emailVerifier = require("verifier-node"); | |
module.exports = function (user, context, cb) { | |
var response = {}; | |
emailVerifier.verify(user.email, context.webtask.secrets.VERIFIER_APIKEY) | |
.then(response => { | |
if (!response.valid()) return cb(new Error('Disposable email!')); | |
response.user = user; |
'use latest'; | |
import express from 'express'; | |
import { fromExpress } from 'webtask-tools'; | |
import bodyParser from 'body-parser'; | |
const app = express(); | |
var jwt = require('express-jwt'); | |
var jwtCheck = jwt({ |
The Webtask Editor is a web based editor (and soon an Electron desktop app) to create and edit webtasks. This started as a side project but it quickly became clear that the editor would help adopt the serverless concept webtask Our goal is to reduce the time it takes to go from an idea => code => HTTPS endpoint.
One of the tools many of us enjoyed using a lot in the old days was the SQL Explorer. The instant feedback you've got when executing queries was great. Edit your query, CTRL+R, see the result, teak the query, CTRL+R, and repeat that loop until you got it right.
This is preliminary feature to add rules into the Client Credentials exchange pipeline (i.e. exchange a client_id and secret for an access_token).
To create a rule that runs on the client credentials exchange you have to use the webtask CLI (wt
). To install the CLI, you can follow the steps here: https://manage.auth0.com/#/account/webtasks.
Assuming you have an API defined with scopes (https://manage.auth0.com/#/apis) and you created a non-interactive client (https://manage.auth0.com/#/applications) and authorized it to use that API, follow these steps to create a rule.
Currenlt you can create only one rule that will be executed for all clients and APIs.
myrule.js
and enter the following. This is an example rule that will add an arbitrary claim (https://foo.com/claim
) to the access_token and will also add an extra scope to the default scopes configured on the API (https://Note: you can change the scopes on the Scope field on Auth0 and include any of these: https://api.slack.com/docs/oauth-scopes
You can now use the Slack connection using any Auth0 client library. Example:
<button class="pay">Pay</button> | |
<script src="https://checkout.stripe.com/checkout.js"> | |
<script> | |
var handler = StripeCheckout.configure({ | |
key: window.STRIPE_PUBLICK_KEY, | |
image: 'https://yourlogo.png', | |
locale: 'auto', | |
token: function(token) { | |
$('.pay').prop("disabled", true); |
This is a comparison of two testing approaches: Runscope service and pure Node.js coding. Written by Hernan Meydac Jean (@VerlicRedclaw)
This service provides a simple to use editor to create API tests with no effort.