Create Constituent with Bloomerang API on New Card Created On Board from Planview Leankit API

Pipedream makes it easy to connect APIs for Bloomerang, Planview Leankit and 2,700+ other apps remarkably fast.

Trigger workflow on

New Card Created On Board from the Planview Leankit API

Next, do this

Create Constituent with the Bloomerang 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 Planview Leankit trigger and Bloomerang action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Card Created On Board trigger
1. Connect your Planview Leankit account
2. Configure Polling interval
3. Select a Board Id
Configure the Create Constituent action
1. Connect your Bloomerang account
2. Select a Constituent Type
3. Optional- Select a Status
4. Configure Organization Name
5. Configure First Name
6. Configure Last Name
7. Optional- Configure Middle Name
8. Optional- Select a Title
9. Optional- Select a Suffix
10. Optional- Configure Job Title
11. Optional- Select a Gender
12. Optional- Configure Birthdate
13. Optional- Configure Employer
14. Optional- Configure Website
15. Optional- Configure Facebook
16. Optional- Configure Twitter ID
17. Optional- Configure LinkedIn
18. Optional- Select a Preferred Communication Channel
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 Card Created On Board on Planview Leankit

Description:Emit new event when a card is created on a board.

Version:0.0.1

Key:planview_leankit-card-created-on-board

View on GitHub

Planview Leankit Overview#

Planview LeanKit API empowers users to automate and integrate their Kanban workflow management. With this API, you can programmatically access boards, cards, and related data to sync with other systems, trigger actions based on board updates, and extract analytics for reporting purposes.

Trigger Code#

import common from "../common/base.mjs";

export default {
  ...common,
  key: "planview_leankit-card-created-on-board",
  name: "New Card Created On Board",
  description: "Emit new event when a card is created on a board.",
  type: "source",
  version: "0.0.1",
  dedupe: "unique",
  props: {
    ...common.props,
  },
  methods: {
    ...common.methods,
    getFunc() {
      return this.planviewLeankit.listActivity;
    },
    validate(d) {
      return d.type === "cardCreated";
    },
    getSummary(data) {
      return `Card '${data.data.card.title}' was created on the board '${this.boardId.label}'`;
    },
  },
};

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
Planview Leankit	`planviewLeankit`	`app`	This component uses the Planview Leankit app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
Polling interval	`timer`	`$.interface.timer`	Pipedream will poll the Monday API on this schedule
Board Id	`boardId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

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

Planview requires users to enter the email and password they use for their Planview account in order to access their API programmatically. For more information, refer to the Planview documentation

Pipedream recommends using a strong and unique password for your Planview account.

About Planview Leankit#

Planview LeanKit enables organizations and teams to visually track and manage the flow of work from strategy to delivery in enterprise Kanban boards. Share a consolidated view of work priority and status – whether in the same room or distributed across the globe.

Action#

Create Constituent on Bloomerang

Description:Creates a new constituent in Bloomerang. [See the documentation](https://bloomerang.co/product/integrations-data-management/api/rest-api/#/Constituents/post_constituent)

Version:0.0.1

Key:bloomerang-create-constituent

View on GitHub

Action Code#

import bloomerang from "../../bloomerang.app.mjs";
import {
  COMMUNICATION_CHANNEL_OPTIONS,
  CONSTITUENT_GENDER_OPTIONS,
  CONSTITUENT_PREFIX_OPTIONS,
  CONSTITUENT_STATUS_OPTIONS,
  CONSTITUENT_SUFFIX_OPTIONS,
  CONSTITUENT_TYPE_OPTIONS,
} from "../../common/constants.mjs";

export default {
  key: "bloomerang-create-constituent",
  name: "Create Constituent",
  description: "Creates a new constituent in Bloomerang. [See the documentation](https://bloomerang.co/product/integrations-data-management/api/rest-api/#/Constituents/post_constituent)",
  version: "0.0.1",
  type: "action",
  props: {
    bloomerang,
    type: {
      type: "string",
      label: "Constituent Type",
      description: "Filter constituents by type",
      options: CONSTITUENT_TYPE_OPTIONS,
      reloadProps: true,
    },
    status: {
      type: "string",
      label: "Status",
      description: "The status of the constituent",
      options: CONSTITUENT_STATUS_OPTIONS,
      optional: true,
    },
    fullName: {
      type: "string",
      label: "Organization Name",
      description: "The organization's name of the constituent",
      hidden: true,
    },
    firstName: {
      type: "string",
      label: "First Name",
      description: "The first name of the constituent",
      hidden: true,
    },
    lastName: {
      type: "string",
      label: "Last Name",
      description: "The last name of the constituent",
      hidden: true,
    },
    middleName: {
      type: "string",
      label: "Middle Name",
      description: "The middle name of the constituent",
      optional: true,
    },
    prefix: {
      type: "string",
      label: "Title",
      description: "The prefix of the constituent",
      options: CONSTITUENT_PREFIX_OPTIONS,
      optional: true,
    },
    suffix: {
      type: "string",
      label: "Suffix",
      description: "The suffix of the constituent",
      options: CONSTITUENT_SUFFIX_OPTIONS,
      optional: true,
    },
    jobTitle: {
      type: "string",
      label: "Job Title",
      description: "The job title of the constituent",
      optional: true,
    },
    gender: {
      type: "string",
      label: "Gender",
      description: "The gender of the constituent",
      options: CONSTITUENT_GENDER_OPTIONS,
      optional: true,
    },
    birthdate: {
      type: "string",
      label: "Birthdate",
      description: "The birth date of the constituent",
      optional: true,
    },
    employer: {
      type: "string",
      label: "Employer",
      description: "The employer of the constituent",
      optional: true,
    },
    website: {
      type: "string",
      label: "Website",
      description: "An website of the constituent",
      optional: true,
    },
    facebookId: {
      type: "string",
      label: "Facebook",
      description: "The constituent's facebook page",
      optional: true,
    },
    twitterId: {
      type: "string",
      label: "Twitter ID",
      description: "The constituent's twitter ID",
      optional: true,
    },
    linkedInId: {
      type: "string",
      label: "LinkedIn",
      description: "The constituent's linkedIn page",
      optional: true,
    },
    preferredCommunicationChannel: {
      type: "string",
      label: "Preferred Communication Channel",
      description: "The preferred comunication channel of the constituent",
      options: COMMUNICATION_CHANNEL_OPTIONS,
      optional: true,
    },
  },
  async additionalProps(props) {
    const isIndividual = this.type === "Individual";
    props.firstName.hidden = !isIndividual;
    props.lastName.hidden = !isIndividual;
    props.fullName.hidden = isIndividual;
    return {};
  },
  async run({ $ }) {
    const data = {
      Type: this.type,
      Status: this.status,
      Prefix: this.prefix,
      Suffix: this.suffix,
      JobTitle: this.jobTitle,
      Gender: this.gender,
      Birthdate: this.birthdate,
      Employer: this.employer,
      Website: this.website,
      FacebookId: this.facebookId,
      TwitterId: this.twitterId,
      LinkedInId: this.linkedInId,
      PreferredCommunicationChannel: this.preferredCommunicationChannel,
    };
    if (this.type === "Individual") {
      data.FirstName = this.firstName;
      data.LastName = this.lastName;
      data.MiddleName = this.middleName;
    } else {
      data.FullName = this.fullName;
    }

    const response = await this.bloomerang.createConstituent({
      $,
      data,
    });

    $.export("$summary", `Successfully created constituent with ID ${response.Id}`);
    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
Bloomerang	`bloomerang`	`app`	This component uses the Bloomerang app.
Constituent Type	`type`	`string`	Select a value from the drop down menu:`IndividualOrganization`
Status	`status`	`string`	Select a value from the drop down menu:`ActiveInactiveDeceased`
Middle Name	`middleName`	`string`	The middle name of the constituent
Title	`prefix`	`string`	Select a value from the drop down menu:`Atty.CaptCmdrCoachColDr.Fr.GenGov.Hon.LtMajMasterMissMr.Mrs.Ms.Mx.PastorPres.Prof.PvtRabbiRep.Rev.Sen.SgtSirSr.`
Suffix	`suffix`	`string`	Select a value from the drop down menu:`DDSEsq.IIIIIIVJr.M.D.Ph.D.Sr.V`
Job Title	`jobTitle`	`string`	The job title of the constituent
Gender	`gender`	`string`	Select a value from the drop down menu:`MaleFemaleOther`
Birthdate	`birthdate`	`string`	The birth date of the constituent
Employer	`employer`	`string`	The employer of the constituent
Website	`website`	`string`	An website of the constituent
Facebook	`facebookId`	`string`	The constituent's facebook page
Twitter ID	`twitterId`	`string`	The constituent's twitter ID
LinkedIn	`linkedInId`	`string`	The constituent's linkedIn page
Preferred Communication Channel	`preferredCommunicationChannel`	`string`	Select a value from the drop down menu:`EmailPhoneText MessageMail`

Action Authentication#

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

About Bloomerang#

Bloomerang Donor Management and Fundraising Software for Nonprofits

More Ways to Connect Bloomerang + Planview Leankit#

Other Popular Integrations#

Create Constituent with Bloomerang API on New Card Created In A Specific Lane from Planview Leankit API

Planview Leankit + Bloomerang

Create Constituent with Bloomerang API on New Card Created On Board from Planview Leankit API

Pipedream makes it easy to connect APIs for Bloomerang, Planview Leankit and 2,700+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of2,700+apps by most popular

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