Automate Your Workflow: Connecting Gmail, Slack, and HTTP with puq.ai

Modern businesses rely on interconnected tools to manage operations, communications, and data pipelines. Yet, manually linking these tools often results in redundant workflows, delayed actions, and human error. puq.ai addresses this challenge by providing a modular, AI-enhanced automation platform that enables seamless integration between services such as Gmail, Slack, and HTTP-based APIs.

This post provides a technical walkthrough of how puq.ai can be used to automate workflows across commonly used platforms, with a focus on constructing robust integrations using Gmail, Slack, and HTTP Request nodes.

Overview of puq.ai Capabilities

puq.ai is a scalable, no-code automation platform with the following core features:

- Visual Flow Builder: Drag-and-drop interface for rapid workflow construction

- Integrated AI Nodes: NLP, classification, summarization, and generation

- Modular Integrations: Gmail, Slack, Discord, HTTP, Notion, Sheets, etc.

- Conditional Logic Support: If/else branching, loops, and path splitting

- Token Management: Secure OAuth2 and API key storage for connected services

- Event-Driven Architecture: Real-time trigger-response pipelines

Use Case: Forwarding Specific Gmail Messages to Slack via puq.ai

Objective

Build an automated flow that:

1. Monitors Gmail for new incoming emails from a defined sender

2. Sends a message to a specific Slack channel with the parsed content

3. (Optionally) Makes an HTTP call to enrich or validate the data before delivery

Step-by-Step Implementation

1. Initialize Workflow

- Navigate to [https://puq.ai](https://puq.ai) and authenticate

- Select `+ New Workflow` > `Blank Flow`

Each flow consists of nodes connected via data pipelines. Begin with a trigger node.

2. Add Gmail Trigger

- Add a new node: Gmail → New Email Received

- Authenticate using OAuth 2.0 or access token

- Set filter criteria:

- From: `[email protected]`

- Subject: Contains `Proposal`

- Enable polling frequency (e.g., every 5 minutes)

The Gmail node will output metadata such as `sender`, `subject`, `body`, `timestamp`, `threadId`, and `attachments`.

3. (Optional) Add HTTP Request Node

- Insert `HTTP Request` node

- Configure HTTP GET/POST:

{

  "url": "https://api.company.com/validate-email",

  "method": "POST",

  "headers": {

    "Authorization": "Bearer {{secure_token}}",

    "Content-Type": "application/json"

  },

  "body": {

    "email": "{{sender}}",

    "message": "{{body}}"

  }

}