Add or Update User with AcyMailing API on New Issue Status Updated (Instant) from Linear (API key) API

Pipedream makes it easy to connect APIs for AcyMailing, Linear (API key) and 2,500+ other apps remarkably fast.

Trigger workflow on

New Issue Status Updated (Instant) from the Linear (API key) API

Next, do this

Add or Update User with the AcyMailing 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 Linear (API key) trigger and AcyMailing action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Issue Status Updated (Instant) trigger
1. Connect your Linear (API key) account
2. Select a Team ID
3. Optional- Select a Project
4. Optional- Select a State (Status)
Configure the Add or Update User action
1. Connect your AcyMailing account
2. Configure Email
3. Optional- Configure Name
4. Optional- Configure Active
5. Optional- Configure Confirmed
6. Optional- Configure CMS Id
7. Optional- Configure Custom Fields
8. Optional- Configure Triggers
9. Optional- Configure Send Conf
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 Issue Status Updated (Instant) on Linear (API key)

Description:Emit new event when the status of an issue is updated. [See the documentation](https://developers.linear.app/docs/graphql/webhooks)

Version:0.1.10

Key:linear_app-new-issue-status-updated

View on GitHub

Linear (API key) Overview#

Linear helps streamline software project management, bug tracking, and task coordination. By using the Linear (API key) API with Pipedream, you can automate routine tasks, sync issues across platforms, and trigger custom workflows. Think auto-assignment of tasks based on specific triggers or pushing updates to a Slack channel when an issue's status changes. These automations save time and ensure that your development team stays focused on coding rather than on administrative overhead.

Trigger Code#

import common from "../common/webhook.mjs";
import constants from "../../common/constants.mjs";
import utils from "../../common/utils.mjs";

export default {
  ...common,
  key: "linear_app-new-issue-status-updated",
  name: "New Issue Status Updated (Instant)",
  description: "Emit new event when the status of an issue is updated. [See the documentation](https://developers.linear.app/docs/graphql/webhooks)",
  type: "source",
  version: "0.1.10",
  dedupe: "unique",
  props: {
    linearApp: common.props.linearApp,
    db: "$.service.db",
    teamId: {
      label: "Team ID",
      type: "string",
      propDefinition: [
        common.props.linearApp,
        "teamId",
      ],
      reloadProps: true,
    },
    projectId: {
      propDefinition: [
        common.props.linearApp,
        "projectId",
      ],
    },
    stateId: {
      propDefinition: [
        common.props.linearApp,
        "stateId",
        ({ teamId }) => ({
          teamId,
        }),
      ],
      description: "Emit issues that are updated to this state",
    },
  },
  methods: {
    ...common.methods,
    _getPreviousStatuses() {
      return this.db.get("previousStatuses") || {};
    },
    _setPreviousStatuses(previousStatuses) {
      this.db.set("previousStatuses", previousStatuses);
    },
    getResourceTypes() {
      return [
        constants.RESOURCE_TYPE.ISSUE,
      ];
    },
    getWebhookLabel() {
      return "Issue status updated";
    },
    getResourcesFn() {
      return this.linearApp.listIssues;
    },
    getResourcesFnArgs() {
      return {
        sortBy: "updatedAt",
        filter: {
          team: this.teamId && {
            id: {
              in: [
                this.teamId,
              ],
            },
          },
          project: {
            id: {
              eq: this.projectId,
            },
          },
          state: {
            id: {
              eq: this.stateId,
            },
          },
        },
      };
    },
    isRelevant(body) {
      return body?.updatedFrom?.stateId && (!this.stateId || body.data.stateId === this.stateId);
    },
    getResource(issue) {
      return this.linearApp.getIssue({
        issueId: issue.id,
      });
    },
    getMetadata(resource) {
      const {
        delivery,
        title,
        data,
        updatedAt,
      } = resource;
      const ts = Date.parse(updatedAt);
      return {
        id: delivery || `${resource.id}-${ts}`,
        summary: `Issue status updated: ${data?.title || title}`,
        ts,
      };
    },
    async emitPolledResources() {
      const previousStatuses = this._getPreviousStatuses();
      const newStatuses = {};

      // Use the specified limit or default to a reasonable number
      const maxLimit = this.limit || constants.DEFAULT_NO_QUERY_LIMIT;

      const stream = this.linearApp.paginateResources({
        resourcesFn: this.getResourcesFn(),
        resourcesFnArgs: this.getResourcesFnArgs(),
        useGraphQl: this.useGraphQl(),
        max: maxLimit, // Use the configured limit instead of hardcoded 1000
      });
      const resources = await utils.streamIterator(stream);

      const updatedResources = [];
      for (const issue of resources) {
        newStatuses[issue.id] = issue.state.id;
        if (issue.createdAt === issue.updatedAt) {
          continue;
        }
        if (previousStatuses[issue.id] !== issue.state.id) {
          updatedResources.push(issue);
        }
      }

      this._setPreviousStatuses(newStatuses);

      updatedResources
        .reverse()
        .forEach((resource) => {
          this.$emit(resource, this.getMetadata(resource));
        });
    },
  },
};

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
Linear (API key)	`linearApp`	`app`	This component uses the Linear (API key) app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Team ID	`teamId`	`string`	Select a value from the drop down menu.
Project	`projectId`	`string`	Select a value from the drop down menu.
State (Status)	`stateId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

About Linear (API key)#

Linear helps streamline software projects, sprints, tasks, and bug tracking. It's built for high-performance teams.

Action#

Add or Update User on AcyMailing

Description:Creates a new user or updates an existing user in AcyMailing. If the user exists, will update the user's data with provided information. [See the documentation](https://docs.acymailing.com/v/rest-api/users#create-or-update-a-user)

Version:0.0.1

Key:acymailing-add-update-user

View on GitHub

Action Code#

import acymailing from "../../acymailing.app.mjs";
import { parseObject } from "../../common/utils.mjs";

export default {
  key: "acymailing-add-update-user",
  name: "Add or Update User",
  description: "Creates a new user or updates an existing user in AcyMailing. If the user exists, will update the user's data with provided information. [See the documentation](https://docs.acymailing.com/v/rest-api/users#create-or-update-a-user)",
  version: "0.0.1",
  type: "action",
  props: {
    acymailing,
    email: {
      type: "string",
      label: "Email",
      description: "The email address is used when updating an existing user.",
    },
    name: {
      type: "string",
      label: "Name",
      description: "Any character should be available.",
      optional: true,
    },
    active: {
      type: "boolean",
      label: "Active",
      description: "Defaults to true.",
      optional: true,
    },
    confirmed: {
      type: "boolean",
      label: "Confirmed",
      description: "The confirmation is related to the \"Require confirmation\" option in the configuration, tab \"Subscription\".",
      optional: true,
    },
    cmsId: {
      type: "integer",
      label: "CMS Id",
      description: "The cms_id must match the ID of the corresponding Joomla/WordPress user.",
      optional: true,
    },
    customFields: {
      type: "object",
      label: "Custom Fields",
      description: "An object of field Ids and values.",
      optional: true,
    },
    triggers: {
      type: "boolean",
      label: "Triggers",
      description: "Defaults to true. Defines if the saving of the user triggers automated tasks like follow-up campaigns and automations.",
      optional: true,
    },
    sendConf: {
      type: "boolean",
      label: "Send Conf",
      description: "Defaults to true. Defines if the confirmation email should be sent when a new user is created.",
      optional: true,
    },
  },
  async run({ $ }) {
    const response = await this.acymailing.createUserOrUpdate({
      $,
      data: {
        email: this.email,
        name: this.name,
        active: this.active,
        confirmed: this.confirmed,
        cmsId: this.cmsId,
        customFields: parseObject(this.customFields),
        triggers: this.triggers,
        sendConf: this.sendConf,
      },
    });
    $.export("$summary", `Successfully added or updated user with email with Id: ${response.userId}`);
    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
AcyMailing	`acymailing`	`app`	This component uses the AcyMailing app.
Email	`email`	`string`	The email address is used when updating an existing user.
Name	`name`	`string`	Any character should be available.
Active	`active`	`boolean`	Defaults to true.
Confirmed	`confirmed`	`boolean`	The confirmation is related to the "Require confirmation" option in the configuration, tab "Subscription".
CMS Id	`cmsId`	`integer`	The cms_id must match the ID of the corresponding Joomla/WordPress user.
Custom Fields	`customFields`	`object`	An object of field Ids and values.
Triggers	`triggers`	`boolean`	Defaults to true. Defines if the saving of the user triggers automated tasks like follow-up campaigns and automations.
Send Conf	`sendConf`	`boolean`	Defaults to true. Defines if the confirmation email should be sent when a new user is created.

Add or Update User with AcyMailing API on New Issue Status Updated (Instant) from Linear (API key) API

Pipedream makes it easy to connect APIs for AcyMailing, Linear (API key) and 2,500+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of2,500+apps by most popular

1
-
24
of
2,500+
apps by most popular