Update Exhibitor with ExpoFP API on New Requests (Payload Only) from HTTP / Webhook API

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

Trigger workflow on

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

Next, do this

Update Exhibitor with the ExpoFP 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 ExpoFP 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 Update Exhibitor action
1. Connect your ExpoFP account
2. Select a Event ID
3. Optional- Configure Name
4. Optional- Configure Description
5. Optional- Configure Featured
6. Optional- Configure Advertised
7. Optional- Configure Country
8. Optional- Configure Address
9. Optional- Configure City
10. Optional- Configure State
11. Optional- Configure ZIP
12. Optional- Configure Phone
13. Optional- Configure Public email
14. Optional- Configure Private email
15. Optional- Configure Website
16. Optional- Configure Contact name
17. Optional- Configure Contact phone
18. Optional- Configure Admin Notes
19. Select a Exhibitor ID
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#

Update Exhibitor on ExpoFP

Description:Updates an exhibitor. [See the documentation](https://expofp.docs.apiary.io/#reference/0/update-exhibitor/update-exhibitor)

Version:0.0.3

Key:expofp-update-exhibitor

View on GitHub

ExpoFP Overview#

The ExpoFP API enables developers to integrate floor plan management and interaction within their applications. With this API, you can access detailed information about exhibition spaces, including booth details, exhibitor information, and floor plan layouts. When you combine ExpoFP with Pipedream's serverless integration and compute platform, you can automate event management tasks, synchronize floor plan data with other systems, and enhance visitor engagement by connecting with CRM or marketing automation tools.

Action Code#

import expofp from "../../expofp.app.mjs";
import common from "../common/add-or-update-exhibitor.mjs";

export default {
  ...common,
  name: "Update Exhibitor",
  version: "0.0.3",
  key: "expofp-update-exhibitor",
  description: "Updates an exhibitor. [See the documentation](https://expofp.docs.apiary.io/#reference/0/update-exhibitor/update-exhibitor)",
  type: "action",
  methods: {
    async updateExhibitor(args) {
      return this.expofp._makeRequest({
        path: "/update-exhibitor",
        method: "post",
        ...args,
      });
    },
  },
  props: {
    ...common.props,
    exhibitorId: {
      propDefinition: [
        expofp,
        "exhibitorId",
        (c) => ({
          eventId: c.eventId,
        }),
      ],
    },
  },
  async run({ $ }) {
    const response = await this.updateExhibitor({
      $,
      data: {
        ...this.getCommonParams(),
        id: this.exhibitorId,
      },
    });

    $.export("$summary", `Successfully updated exhibitor with ID ${this.exhibitorId}`);

    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
ExpoFP	`expofp`	`app`	This component uses the ExpoFP app.
Event ID	`eventId`	`string`	Select a value from the drop down menu.
Name	`name`	`string`	Name of the exhibitor
Description	`description`	`string`	Description of the exhibitor
Featured	`featured`	`boolean`	Exhibitor is featured
Advertised	`advertised`	`boolean`	Exhibitor is advertised
Country	`country`	`string`	Country of the exhibitor
Address	`address`	`string`	Address of the exhibitor
City	`city`	`string`	City of the exhibitor
State	`state`	`string`	State of the exhibitor
ZIP	`zip`	`string`	ZIP code of the exhibitor
Phone	`phone`	`string`	Phone of the exhibitor
Public email	`publicEmail`	`string`	Public email of the exhibitor
Private email	`privateEmail`	`string`	Private email of the exhibitor
Website	`website`	`string`	Website of the exhibitor
Contact name	`contactName`	`string`	Contact name of the exhibitor
Contact phone	`contactPhone`	`string`	Contact phone of the exhibitor
Admin Notes	`adminNotes`	`string`	Admin notes for the exhibitor
Exhibitor ID	`exhibitorId`	`string`	Select a value from the drop down menu.

Action Authentication#

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

To retrieve your API Token,

Navigate to your ExpoFP account and sign in
Go to “Profile” > “API Token”

About ExpoFP#

Create interactive Expo floor plans

More Ways to Connect ExpoFP + HTTP / Webhook#

Other Popular Integrations#

Get Booth with ExpoFP API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + ExpoFP

Try it

Get Booth with ExpoFP API on New Requests from HTTP / Webhook API

HTTP / Webhook + ExpoFP

Try it

Get Exhibitor with ExpoFP API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + ExpoFP

Try it

Get Exhibitor with ExpoFP API on New Requests from HTTP / Webhook API

HTTP / Webhook + ExpoFP

Try it

Get Booth with ExpoFP API on New event when the content of the URL changes. from HTTP / Webhook API

HTTP / Webhook + ExpoFP

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