Create Lead with Rex API on New Requests (Payload Only) from HTTP / Webhook API

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

Trigger workflow on

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

Next, do this

Create Lead with the Rex 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 Rex 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 (Payload Only) trigger
1. Connect your HTTP / Webhook account
Configure the Create Lead action
1. Connect your Rex account
2. Select a Lead Type
3. Select a Contact
4. Select a Source
5. Configure Note
6. Optional- Select a Listing
7. Optional- Select a Property
8. Optional- Select a Project
9. Optional- Select a Project Stage
10. Optional- Select a Assignee
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 (Payload Only) on HTTP / Webhook

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

Version:0.1.1

Key:http-new-requests-payload-only

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
// Returns a 200 OK response, emits the HTTP payload as an event
export default {
  key: "http-new-requests-payload-only",
  name: "New Requests (Payload Only)",
  // eslint-disable-next-line
  description: "Get a URL and emit the HTTP body as an event on every request",
  version: "0.1.1",
  type: "source",
  props: {
    // eslint-disable-next-line
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    http,
  },
  async run(event) {
    const { body } = event;
    this.httpInterface.respond({
      status: 200,
      body,
    });
    // Emit the HTTP payload
    this.$emit({
      body,
    });
  },
};

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.
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#

Create Lead on Rex

Description:Creates a new lead in Rex. [See the documentation](https://api-docs.rexsoftware.com/service/leads#operation/create)

Version:0.0.1

Key:rex-create-lead

View on GitHub

Rex Overview#

The Rex API allows for automation and integration of real estate CRM functionalities within the Pipedream platform. By leveraging Rex, you can streamline operations, synchronize data across various platforms, and trigger actions within the Rex ecosystem based on events from other apps or services. Whether you're managing listings, contacts, or marketing efforts, the Rex API on Pipedream can be a powerful tool to enhance productivity and customer engagement in real estate businesses.

Action Code#

import rex from "../../rex.app.mjs";
import constants from "../../common/constants.mjs";

export default {
  key: "rex-create-lead",
  name: "Create Lead",
  description: "Creates a new lead in Rex. [See the documentation](https://api-docs.rexsoftware.com/service/leads#operation/create)",
  version: "0.0.1",
  type: "action",
  props: {
    rex,
    leadType: {
      type: "string",
      label: "Lead Type",
      description: "The type of lead",
      options: constants.LEAD_TYPE_OPTIONS,
    },
    contactId: {
      propDefinition: [
        rex,
        "contactId",
      ],
    },
    sourceId: {
      propDefinition: [
        rex,
        "sourceId",
      ],
    },
    note: {
      type: "string",
      label: "Note",
      description: "Message filled in by the user about the reason for contact",
    },
    listingId: {
      propDefinition: [
        rex,
        "listingId",
      ],
    },
    propertyId: {
      propDefinition: [
        rex,
        "propertyId",
      ],
    },
    projectId: {
      propDefinition: [
        rex,
        "projectId",
      ],
    },
    projectStageId: {
      propDefinition: [
        rex,
        "projectStageId",
      ],
    },
    assigneeId: {
      propDefinition: [
        rex,
        "userId",
      ],
      label: "Assignee",
      description: "Identifier of the account/agent that will manage the lead",
      optional: true,
    },
  },
  async run({ $ }) {
    const data = {
      data: {
        note: this.note,
        lead_type: {
          id: this.leadType,
        },
        contact: {
          id: this.contactId,
        },
        lead_source: {
          id: this.sourceId,
        },
        listing: this.listingId
          ? {
            id: this.listingId,
          }
          : undefined,
        property: this.propertyId
          ? {
            id: this.propertyId,
          }
          : undefined,
        project: this.projectId
          ? {
            id: this.projectId,
          }
          : undefined,
        project_stage: this.projectStageId
          ? {
            id: this.projectStageId,
          }
          : undefined,
        assignee: this.assigneeId
          ? {
            id: this.assigneeId,
          }
          : undefined,
      },
    };

    const { result } = await this.rex.createLead({
      data,
      $,
    });

    if (result?.id) {
      $.export("$summary", `Successfully created lead with ID ${result.id}.`);
    }

    return result;
  },
};

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
Rex	`rex`	`app`	This component uses the Rex app.
Lead Type	`leadType`	`string`	Select a value from the drop down menu:`{ "value": "general", "label": "General" }{ "value": "appraisal_request", "label": "Appraisal Request" }{ "value": "listing_enquiry", "label": "Listing Enquiry" }`
Contact	`contactId`	`string`	Select a value from the drop down menu.
Source	`sourceId`	`string`	Select a value from the drop down menu.
Note	`note`	`string`	Message filled in by the user about the reason for contact
Listing	`listingId`	`string`	Select a value from the drop down menu.
Property	`propertyId`	`string`	Select a value from the drop down menu.
Project	`projectId`	`string`	Select a value from the drop down menu.
Project Stage	`projectStageId`	`string`	Select a value from the drop down menu.
Assignee	`assigneeId`	`string`	Select a value from the drop down menu.

Action Authentication#

Rex uses OAuth authentication. When you connect your Rex account, Pipedream will open a popup window where you can sign into Rex and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Rex API.

Pipedream requests the following authorization scopes when you connect your account:

About Rex#

The real estate software platform built for all your agency needs.

More Ways to Connect Rex + HTTP / Webhook#

Other Popular Integrations#

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

HTTP / Webhook + Rex