Transcribe Video with Hamsa API on New Requests from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Hamsa, HTTP / Webhook and 2,500+ other apps remarkably fast.

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

Transcribe Video with the Hamsa API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a HTTP / Webhook trigger and Hamsa action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Requests trigger
1. Optional- Configure Body Only
2. Optional- Configure Response Status Code
3. Optional- Configure Response Content-Type
4. Optional- Configure Response Body
5. Connect your HTTP / Webhook account
Configure the Transcribe Video action
1. Connect your Hamsa account
2. Configure Media URL
3. Select a Model
4. Optional- Configure Webhook URL
5. Optional- Configure Webhook Auth Key
6. Optional- Configure Webhook Auth Secret
7. Optional- Configure Title
8. Optional- Select a Language
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Requests on HTTP / Webhook

Description: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.

Version:0.1.1

Key:http-new-requests

View on GitHub

HTTP / Webhook Overview#

Build, test, and send HTTP requests without code using your Pipedream workflows. The HTTP / Webhook action is a tool to build HTTP requests with a Postman-like graphical interface.

Point and click HTTP requests

Define the target URL, HTTP verb, headers, query parameters, and payload body without writing custom code.

$A screenshot of Pipedream's HTTP Request Configuration interface with a GET request type selected. The request URL is set to 'https://api.openai.com/v1/models'. The 'Auth' tab is highlighted, indicating that authentication is required for this request. In the headers section, there are two headers configured: 'User-Agent' is set to 'pipedream/1', and 'Authorization' is set to 'Bearer {{openai_api_key}}', showing how the OpenAI account's API key is dynamically inserted into the headers to handle authentication automatically.$

Here's an example workflow that uses the HTTP / Webhook action to send an authenticated API request to OpenAI.

Focus on integrating, not authenticating

This action can also use your connected accounts with third-party APIs. Selecting an integrated app will automatically update the request’s headers to authenticate with the app properly, and even inject your token dynamically.

Pipedream integrates with thousands of APIs, but if you can’t find a Pipedream integration simply use Environment Variables in your request headers to authenticate with.

Compatible with no code actions or Node.js and Python

The HTTP/Webhook action exports HTTP response data for use in subsequent workflow steps, enabling easy data transformation, further API calls, database storage, and more.

Response data is available for both coded (Node.js, Python) and no-code steps within your workflow.

Trigger Code#

import http from "../../http.app.mjs";

// Core HTTP component
export default {
  key: "http-new-requests",
  name: "New Requests",
  description: "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.",
  version: "0.1.1",
  type: "source",
  props: {
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    emitBodyOnly: {
      type: "boolean",
      label: "Body Only",
      description: "This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.",
      optional: true,
      default: false,
    },
    resStatusCode: {
      type: "string",
      label: "Response Status Code",
      description: "The status code to return in the HTTP response",
      optional: true,
      default: "200",
    },
    resContentType: {
      type: "string",
      label: "Response Content-Type",
      description: "The `Content-Type` of the body returned in the HTTP response",
      optional: true,
      default: "application/json",
    },
    resBody: {
      type: "string",
      label: "Response Body",
      description: "The body to return in the HTTP response",
      optional: true,
      default: "{ \"success\": true }",
    },
    http,
  },
  async run(event) {
    const summary = `${event.method} ${event.path}`;

    this.httpInterface.respond({
      status: this.resStatusCode,
      body: this.resBody,
      headers: {
        "content-type": this.resContentType,
      },
    });

    if (this.emitBodyOnly) {
      this.$emit(event.body, {
        summary,
      });
    } else {
      this.$emit(event, {
        summary,
      });
    }
  },
};

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
N/A	`httpInterface`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
Body Only	`emitBodyOnly`	`boolean`	This source emits an event representing the full HTTP request by default. Select `true` to emit the body only.
Response Status Code	`resStatusCode`	`string`	The status code to return in the HTTP response
Response Content-Type	`resContentType`	`string`	The `Content-Type` of the body returned in the HTTP response
Response Body	`resBody`	`string`	The body to return in the HTTP response
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.

Trigger Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

Get a unique URL where you can send HTTP or webhook requests

Action#

Transcribe Video on Hamsa

Description:Automatically transcribe Arabic videos from YouTube URLs or direct links. [See the documentation](https://docs.tryhamsa.com/api-reference/endpoint/transcribe)

Version:0.0.1

Key:hamsa-transcribe-video

View on GitHub

Action Code#

import {
  LANGUAGE_OPTIONS,
  MODEL_OPTIONS,
} from "../../common/constants.mjs";
import hamsa from "../../hamsa.app.mjs";

export default {
  key: "hamsa-transcribe-video",
  name: "Transcribe Video",
  description: "Automatically transcribe Arabic videos from YouTube URLs or direct links. [See the documentation](https://docs.tryhamsa.com/api-reference/endpoint/transcribe)",
  version: "0.0.1",
  type: "action",
  props: {
    hamsa,
    mediaUrl: {
      type: "string",
      label: "Media URL",
      description: "The URL of the video to be transcribed.",
    },
    model: {
      type: "string",
      label: "Model",
      description: "The model you want to use to transcribe.",
      options: MODEL_OPTIONS,
    },
    webhookUrl: {
      propDefinition: [
        hamsa,
        "webhookUrl",
      ],
      optional: true,
    },
    webhookAuthKey: {
      type: "string",
      label: "Webhook Auth Key",
      description: "The key to use for authenticating the webhook.",
      optional: true,
    },
    webhookAuthSecret: {
      type: "string",
      label: "Webhook Auth Secret",
      description: "The secret to use for authenticating the webhook.",
      secret: true,
      optional: true,
    },
    title: {
      type: "string",
      label: "Title",
      description: "The title of the transcription.",
      optional: true,
    },
    language: {
      type: "string",
      label: "Language",
      description: "The language of the transcription.",
      options: LANGUAGE_OPTIONS,
      optional: true,
    },
  },
  async run({ $ }) {
    const webhookAuth = {};
    if (this.webhookAuthKey) {
      webhookAuth.authKey = this.webhookAuthKey;
    }
    if (this.webhookAuthSecret) {
      webhookAuth.authSecret = this.webhookAuthSecret;
    }
    const data = {
      mediaUrl: this.mediaUrl,
      model: this.model,
      processingType: "async",
      webhookUrl: this.webhookUrl,
      title: this.title,
      language: this.language,
    };
    if (Object.keys(webhookAuth).length) {
      data.webhookAuth = webhookAuth;
    }

    const response = await this.hamsa.transcribeVideo({
      $,
      data,
    });

    $.export("$summary", "Transcription job started successfully.");
    return response;
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Hamsa	`hamsa`	`app`	This component uses the Hamsa app.
Media URL	`mediaUrl`	`string`	The URL of the video to be transcribed.
Model	`model`	`string`	Select a value from the drop down menu:`{ "label": "Hamsa-General-V2.0 - Our most advanced ASR model, optimized for high accuracy across podcasts, videos, and general audio.", "value": "Hamsa-General-V2.0" }{ "label": "Hamsa-Conversational-V1.0 - Best suited for conversational use cases, optimized for accurately transcribing phone calls and meetings.", "value": "Hamsa-Conversational-V1.0" }`
Webhook URL	`webhookUrl`	`string`	The URL to receive the webhook notifications.
Webhook Auth Key	`webhookAuthKey`	`string`	The key to use for authenticating the webhook.
Webhook Auth Secret	`webhookAuthSecret`	`string`	The secret to use for authenticating the webhook.
Title	`title`	`string`	The title of the transcription.
Language	`language`	`string`	Select a value from the drop down menu:`aren`

Action Authentication#

Hamsa uses API keys for authentication. When you connect your Hamsa account, Pipedream securely stores the keys so you can easily authenticate to Hamsa APIs in both code and no-code steps.

About Hamsa#

AI Models That Master Arabic Dialects

More Ways to Connect Hamsa + HTTP / Webhook#

Other Popular Integrations#

Create AI Content with Hamsa API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Hamsa

Try it

Create AI Content with Hamsa API on New Requests from HTTP / Webhook API

HTTP / Webhook + Hamsa

Try it

List Jobs with Hamsa API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Hamsa

Try it

List Jobs with Hamsa API on New Requests from HTTP / Webhook API

HTTP / Webhook + Hamsa

Try it

Synthesize Voice with Hamsa API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Hamsa

Try it

Popular Triggers#

New Requests from the HTTP / Webhook API

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.

Try it

New Requests (Payload Only) from the HTTP / Webhook API

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

Try it

New event when the content of the URL changes. from the HTTP / Webhook API

Emit new event when the content of the URL changes.

Try it