AppsPricingBlogTry it
Seven logo
HTTP / Webhook logo

Connect Seven to HTTP / Webhook

Use 2 documented Seven triggers to run 7 documented HTTP / Webhook actions.

2 source triggers
7 target actions
Reverse direction supported

Why Connect Seven & HTTP / Webhook?

Start with a Seven event

Choose from 2 documented triggers, including New Incoming Call (Instant), New Incoming SMS (Instant).

Run a HTTP / Webhook action

Send the event into one of 7 documented actions, such as Send any HTTP Request, Send GET Request, Send POST Request.

Map and review the workflow

Choose the fields and conditions for the workflow, then test the result before activation.

Available Triggers & Actions

Seven logo

Seven

Triggers (2)

New Incoming Call (Instant)

Emit new event when a voice call occurs. See the documentation

webhook
New Incoming SMS (Instant)

Emit new event when a new inbound SMS is received. See the documentation

webhook

Actions (7)

Get Analytics

Retrieve account statistics (SMS, RCS, voice, HLR, usage). See the documentation

List Subaccounts Options

Retrieves available options for the Subaccounts field.

Lookup CNAM

Look up caller name information via Seven. See the documentation

Lookup Format

Look up phone number formatting via Seven. See the documentation

Lookup HLR

Look up home location register information via Seven. See the documentation

Make TTS Call

Make a text-to-speech call via Seven. See the documentation

Send SMS

Send SMS via Seven. See the documentation

HTTP / Webhook logo

HTTP / Webhook

Triggers (4)

New Requests

Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

polling
New Requests (Payload Only)

Get a URL and emit the HTTP body as an event on every request

polling
New event when the content of the URL changes.

Emit new event when the content of the URL changes.

polling
New Webhook Request

Emit new event when an HTTP request is received at the webhook URL. Use as a trigger to run workflows from external services (GitHub, Stripe, n8n, etc.). Configure response code, body, and which HTTP methods to accept.

webhook

Actions (7)

Send any HTTP Request

Send an HTTP request using any method and URL. Optionally configure query string parameters, headers, and basic auth.

Send GET Request

Send an HTTP GET request to any URL. Optionally configure query string parameters, headers and basic auth.

Send POST Request

Send an HTTP POST request to any URL. Optionally configure query string parameters, headers and basic auth.

Send PUT Request

Send an HTTP PUT request to any URL. Optionally configure query string parameters, headers and basic auth.

Return HTTP Response

Use with an HTTP trigger that uses "Return a custom response from your workflow" as its HTTP Response

Validate Webhook Auth

Require authorization for incoming HTTP webhook requests. Make sure to configure the HTTP trigger to "Return a custom response from your workflow".

Verify HMAC Signature

Validate HMAC signature for incoming HTTP webhook requests. Make sure to configure the HTTP trigger to "Return a custom response from your workflow".

Integration Features

2 documented Seven triggers
7 documented HTTP / Webhook actions
Configurable field mapping
Conditional workflow steps
Execution monitoring
A supported HTTP / Webhook to Seven direction

Capability Examples

Seven trigger → HTTP / Webhook action

Catalog example
SevenSeven

New Incoming Call (Instant)

HTTP / WebhookHTTP / Webhook

Send any HTTP Request

HTTP / Webhook trigger → Seven action

Reverse direction
HTTP / WebhookHTTP / Webhook

New Requests

SevenSeven

Get Analytics

How It Works

1

Connect Apps

Authenticate your Seven and HTTP / Webhook accounts

2

Choose a Trigger

Select a documented Seven event

3

Choose an Action

Select the documented HTTP / Webhook operation to run

Test and Review

Verify field mapping and provider responses before activation

Frequently Asked Questions

Integration Benefits

Trigger-driven Workflows

Start the supported direction from one of 2 documented Seven triggers.

Automated Actions

Run one of 7 documented HTTP / Webhook actions after the selected trigger fires.

Provider Authentication

Review the authentication requirements published by each provider before activating the workflow.

Guided Configuration

Select a documented trigger, choose a target action, and map the fields required by the workflow.

Field Mapping

Map the fields exposed by the selected trigger and action, then review the required provider inputs.

Execution Review

Test the workflow and review provider responses before relying on it in production.

HTTP / Webhook logoSeven logo

Reverse Integration Available

Also connect HTTP / Webhook to Seven for bidirectional automation

View Integration
Seven logo

All Seven Integrations

Explore all available Seven connections

View All Integrations
HTTP / Webhook logo

All HTTP / Webhook Integrations

Explore all available HTTP / Webhook connections

View All Integrations

Ready to Connect Seven & HTTP / Webhook?

Build this supported workflow in Mazaal AI and test it with your own provider accounts.

Get Started Free