Update Deal with OnePageCRM API on New Requests from HTTP / Webhook API

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

Trigger workflow on

New Requests from the HTTP / Webhook API

Next, do this

Update Deal with the OnePageCRM 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 OnePageCRM 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 Update Deal action
1. Connect your OnePageCRM account
2. Select a Deal ID
3. Optional- Select a Contact ID
4. Optional- Select a User ID
5. Optional- Select a Pipeline ID
6. Optional- Configure Name
7. Optional- Configure Text
8. Optional- Select a Stage
9. Optional- Select a Status
10. Optional- Configure Expected Close Date
11. Optional- Configure Close Date
12. Optional- Configure Date
13. Optional- Configure Amount
14. Optional- Configure Months
15. Optional- Configure Cost
16. Optional- Select a Commission Base
17. Optional- Select a Commission Type
18. Optional- Configure Commission
19. Optional- Configure Commission Percentage
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#

Update Deal on OnePageCRM

Description:Updates an existing deal's details in OnePageCRM. [See the documentation](https://developer.onepagecrm.com/api/)

Version:0.0.1

Key:onepagecrm-update-deal

View on GitHub

OnePageCRM Overview#

The OnePageCRM API enables interaction with your OnePageCRM account, automating your contact and sales management. With it, you can create, update, and delete contacts, deals, and notes, or trigger actions based on sales activities. When combined with Pipedream's serverless platform, this API allows you to connect OnePageCRM with hundreds of other apps to streamline your sales process, enhance lead generation, and improve follow-ups.

Action Code#

import { STAGE_OPTIONS } from "../../common/constants.mjs";
import onepagecrm from "../../onepagecrm.app.mjs";

export default {
  key: "onepagecrm-update-deal",
  name: "Update Deal",
  description: "Updates an existing deal's details in OnePageCRM. [See the documentation](https://developer.onepagecrm.com/api/)",
  version: "0.0.1",
  type: "action",
  props: {
    onepagecrm,
    dealId: {
      propDefinition: [
        onepagecrm,
        "dealId",
      ],
    },
    contactId: {
      propDefinition: [
        onepagecrm,
        "contactId",
      ],
      optional: true,
    },
    ownerId: {
      propDefinition: [
        onepagecrm,
        "userId",
      ],
      optional: true,
    },
    pipelineId: {
      propDefinition: [
        onepagecrm,
        "pipelineId",
      ],
      optional: true,
    },
    name: {
      type: "string",
      label: "Name",
      description: "Name of the deal.",
      optional: true,
    },
    text: {
      type: "string",
      label: "Text",
      description: "Extra notes related to the deal (supports [b]bold[/b] and [i]italic[/i] formatting).",
      optional: true,
    },
    stage: {
      type: "integer",
      label: "Stage",
      description: "A numerical representation of the progress of a pending deal.",
      options: STAGE_OPTIONS,
      optional: true,
    },
    status: {
      type: "string",
      label: "Status",
      description: "Status of the deal.",
      options: [
        "pending",
        "won",
        "lost",
      ],
      optional: true,
    },
    expectedCloseDate: {
      type: "string",
      label: "Expected Close Date",
      description: "The date the deal is expected to close. **Format: YYYY-MM-DD**. **(status should be `pending`)**.",
      optional: true,
    },
    closeDate: {
      type: "string",
      label: "Close Date",
      description: "The date the deal actually closed. **(status should be `won` or `lost`)`**.",
      optional: true,
    },
    date: {
      type: "string",
      label: "Date",
      description: "Creation date of the deal.",
      optional: true,
    },
    amount: {
      type: "string",
      label: "Amount",
      description: "The monitary value of the deal (per month, if multi-month deal).",
      optional: true,
    },
    months: {
      type: "integer",
      label: "Months",
      description: "Number of months the deal is to be paid for. (1 for regular deals, 2+ for multi-month).",
      default: 1,
      optional: true,
    },
    cost: {
      type: "string",
      label: "Cost",
      description: "The monitary cost of the deal",
      optional: true,
    },
    commissionBase: {
      type: "string",
      label: "Commission Base",
      description: "Base used to calculate the commission of the deal.",
      options: [
        "amount",
        "margin",
      ],
      optional: true,
    },
    commissionType: {
      type: "string",
      label: "Commission Type",
      description: "Type of commission for the deal.",
      options: [
        "none",
        "percentage",
        "absolute",
      ],
      optional: true,
    },
    commission: {
      type: "string",
      label: "Commission",
      description: "Commission payable for the deal.",
      optional: true,
    },
    commissionPercentage: {
      type: "string",
      label: "Commission Percentage",
      description: "Commission percentage for the deal.",
      optional: true,
    },
  },
  async run({ $ }) {
    const { data: { deal } } = await this.onepagecrm.getDeal({
      $,
      dealId: this.dealId,
    });
    if (this.contactId) deal.contact_id = this.contactId;
    if (this.ownerId) deal.owner_id = this.ownerId;
    if (this.pipelineId) deal.pipeline_id = this.pipelineId;
    if (this.name) deal.name = this.name;
    if (this.text) deal.text = this.text;
    if (this.stage) deal.stage = this.stage;
    if (this.status) deal.status = this.status;
    if (this.expectedCloseDate) deal.expected_close_date = this.expectedCloseDate;
    if (this.closeDate) deal.close_date = this.closeDate;
    if (this.date) deal.date = this.date;
    if (this.amount) deal.amount = this.amount;
    if (this.months) deal.months = this.months;
    if (this.cost) deal.cost = this.cost;
    if (this.commissionBase) deal.commission_base = this.commissionBase;
    if (this.commissionType) deal.commission_type = this.commissionType;
    if (this.commission) deal.commission = this.commission;
    if (this.commissionPercentage) deal.commission_percentage = this.commissionPercentage;

    const response = await this.onepagecrm.updateDeal({
      $,
      dealId: this.dealId,
      data: deal,
    });

    $.export("$summary", `Successfully updated deal with ID ${this.dealId}`);
    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
OnePageCRM	`onepagecrm`	`app`	This component uses the OnePageCRM app.
Deal ID	`dealId`	`string`	Select a value from the drop down menu.
Contact ID	`contactId`	`string`	Select a value from the drop down menu.
User ID	`ownerId`	`string`	Select a value from the drop down menu.
Pipeline ID	`pipelineId`	`string`	Select a value from the drop down menu.
Name	`name`	`string`	Name of the deal.
Text	`text`	`string`	Extra notes related to the deal (supports [b]bold[/b] and [i]italic[/i] formatting).
Stage	`stage`	`integer`	Select a value from the drop down menu:`{ "label": 10, "value": 10 }{ "label": 20, "value": 20 }{ "label": 40, "value": 40 }{ "label": 60, "value": 60 }{ "label": 80, "value": 80 }`
Status	`status`	`string`	Select a value from the drop down menu:`pendingwonlost`
Expected Close Date	`expectedCloseDate`	`string`	The date the deal is expected to close. Format: YYYY-MM-DD. (status should be `pending`).
Close Date	`closeDate`	`string`	The date the deal actually closed. (status should be `won` or `lost`)`.
Date	`date`	`string`	Creation date of the deal.
Amount	`amount`	`string`	The monitary value of the deal (per month, if multi-month deal).
Months	`months`	`integer`	Number of months the deal is to be paid for. (1 for regular deals, 2+ for multi-month).
Cost	`cost`	`string`	The monitary cost of the deal
Commission Base	`commissionBase`	`string`	Select a value from the drop down menu:`amountmargin`
Commission Type	`commissionType`	`string`	Select a value from the drop down menu:`nonepercentageabsolute`
Commission	`commission`	`string`	Commission payable for the deal.
Commission Percentage	`commissionPercentage`	`string`	Commission percentage for the deal.

Action Authentication#

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

To retrieve your User ID and API Key,

Navigate to your Onepage account and sign in
Click the User menu on the top right
Go to “Apps and Integrations” > “Utilities” > “API”
Open the “Configuration” tab

About OnePageCRM#

#1 action-focused CRM software for small business. We help bring action and focus to the chaotic world of sales.

More Ways to Connect OnePageCRM + HTTP / Webhook#

Other Popular Integrations#

Create Contact with OnePageCRM API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + OnePageCRM