Update Activity with Zixflow API on New Requests (Payload Only) from HTTP / Webhook API

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

Trigger workflow on

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

Next, do this

Update Activity with the Zixflow 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 Zixflow 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 Activity action
1. Connect your Zixflow account
2. Select a Activity ID
3. Optional- Select a Icon Type
4. Optional- Select a Icon Value
5. Optional- Configure Schedule At
6. Optional- Configure Activity Name
7. Optional- Configure Description
8. Optional- Select a Status ID
9. Optional- Select a Association Type
10. Optional- Select a Associated 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 Activity on Zixflow

Description:Updates an existing activity or task in Zixflow. [See the documentation](https://docs.zixflow.com/api-reference/activity-list/edit)

Version:0.0.2

Key:zixflow-update-activity

View on GitHub

Zixflow Overview#

The Zixflow API allows for the automation of business process workflows, enabling the creation, management, and optimization of tasks across various functions. Utilizing this API in Pipedream, one can automate repetitive tasks, integrate with other services, and trigger actions based on specific conditions, helping to streamline business operations and increase efficiency.

Action Code#

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

export default {
  key: "zixflow-update-activity",
  name: "Update Activity",
  description: "Updates an existing activity or task in Zixflow. [See the documentation](https://docs.zixflow.com/api-reference/activity-list/edit)",
  version: "0.0.2",
  annotations: {
    destructiveHint: true,
    openWorldHint: true,
    readOnlyHint: false,
  },
  type: "action",
  props: {
    app,
    activityId: {
      propDefinition: [
        app,
        "activityId",
      ],
      reloadProps: true,
    },
    iconType: {
      propDefinition: [
        app,
        "iconType",
      ],
      optional: true,
      reloadProps: true,
    },
    iconValue: {
      propDefinition: [
        app,
        "iconValue",
        (c) => ({
          iconType: c.iconType,
        }),
      ],
      optional: true,
    },
    scheduleAt: {
      propDefinition: [
        app,
        "scheduleAt",
      ],
      optional: true,
    },
    name: {
      propDefinition: [
        app,
        "name",
      ],
      optional: true,
    },
    description: {
      propDefinition: [
        app,
        "description",
      ],
      optional: true,
    },
    statusId: {
      propDefinition: [
        app,
        "statusId",
      ],
      optional: true,
    },
    associationType: {
      propDefinition: [
        app,
        "associationType",
      ],
      optional: true,
    },
    associatedId: {
      propDefinition: [
        app,
        "associatedId",
        (c) => ({
          associationType: c.associationType,
        }),
      ],
      optional: true,
    },
  },
  async additionalProps() {
    const props = {
      iconValue: {
        type: "string",
        label: "Icon Value",
        description: "Defines the specific value of the icon based on the iconType",
      },
    };

    if (this.iconType !== "emoji") {
      props.iconValue.options = this.iconType === "interaction"
        ? constants.INTERACTION_TYPES
        : constants.MESSAGING_TYPES;
    }

    return props;
  },
  async run({ $ }) {
    const response = await this.app.updateActivity({
      $,
      activityId: this.activityId,
      data: {
        iconType: this.iconType,
        iconValue: this.iconValue,
        scheduleAt: this.scheduleAt,
        name: this.name,
        description: this.description,
        status: this.statusId,
        associated: this.associatedId,
      },
    });

    $.export("$summary", `Successfully updated activity with ID ${this.activityId}`);
    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
Zixflow	`app`	`app`	This component uses the Zixflow app.
Activity ID	`activityId`	`string`	Select a value from the drop down menu.
Icon Type	`iconType`	`string`	Select a value from the drop down menu:`{ "label": "Emoji", "value": "emoji" }{ "label": "Interaction", "value": "interaction" }{ "label": "Messaging App", "value": "messaging_app" }`
Icon Value	`iconValue`	`string`	Select a value from the drop down menu.
Schedule At	`scheduleAt`	`string`	Specifies the scheduled time for the activity in the format `YYYY-MM-DDTHH:mm:ss.SSSZ`
Activity Name	`name`	`string`	The name or title of the activity
Description	`description`	`string`	A description providing additional details about the activity
Status ID	`statusId`	`string`	Select a value from the drop down menu.
Association Type	`associationType`	`string`	Select a value from the drop down menu.
Associated ID	`associatedId`	`string`	Select a value from the drop down menu.

Action Authentication#

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

About Zixflow#

AI-CRM and Messaging Across SMS, Email, and WhatsApp.

More Ways to Connect Zixflow + HTTP / Webhook#

Other Popular Integrations#

Create Activity with Zixflow API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Zixflow

Try it

Create Activity with Zixflow API on New Requests from HTTP / Webhook API

HTTP / Webhook + Zixflow

Try it

Delete Activity with Zixflow API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Zixflow

Try it

Delete Activity with Zixflow API on New Requests from HTTP / Webhook API

HTTP / Webhook + Zixflow

Try it

Get Activities with Zixflow API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Zixflow

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