Create Note with Evernote API on New Authorized Purchase Order from DEAR Systems API

Pipedream makes it easy to connect APIs for Evernote, DEAR Systems and 2,700+ other apps remarkably fast.

Trigger workflow on

New Authorized Purchase Order from the DEAR Systems API

Next, do this

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

Select this integration
Configure the New Authorized Purchase Order trigger
1. Connect your DEAR Systems account
Configure the Create Note action
1. Connect your Evernote account
2. Configure Title
3. Optional- Configure Content
4. Optional- Configure Active
5. Optional- Select a Notebook ID
6. Optional- Select one or more Tag IDs
7. Optional- Configure Attributes
8. Optional- Configure No Update Title
9. Optional- Configure No Update Content
10. Optional- Configure No Update Email
11. Optional- Configure No Update Share
12. Optional- Configure No Update Share Publicly
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 Authorized Purchase Order on DEAR Systems

Description:Emit new event when a purchase order is created and authorized

Version:0.0.1

Key:dear-new-authorized-purchase-order

View on GitHub

DEAR Systems Overview#

DEAR Systems offers an API that provides programmatic access to its inventory management platform, allowing for seamless integration with other apps for automating various business processes. Leveraging this API within Pipedream, you can create custom workflows to synchronize inventory levels, manage sales and purchase orders, and automate financial reporting among other tasks. By connecting DEAR Systems to Pipedream’s vast array of supported apps, you can achieve a high degree of automation, reducing manual entry and data errors, and gaining insights from real-time data processing.

Trigger Code#

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

export default {
  ...base,
  name: "New Authorized Purchase Order",
  key: "dear-new-authorized-purchase-order",
  type: "source",
  description: "Emit new event when a purchase order is created and authorized",
  version: "0.0.1",
  dedupe: "unique",
  methods: {
    ...base.methods,
    getWebhookType() {
      return constants.WEBHOOK_TYPE.PURCHASE_ORDER_AUTHORISED;
    },
    getMetadata(payload) {
      const {
        amznTraceId,
        TaskID,
        PurchaseOrderNumber,
      } = payload;

      const compositeId = `${TaskID}-${amznTraceId}`;

      return {
        id: compositeId,
        summary: `A new purchase order with OrderNumber: ${PurchaseOrderNumber} was successfully authorized!`,
        ts: Date.now(),
      };
    },
  },
};

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
DEAR Systems	`dear`	`app`	This component uses the DEAR Systems app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
N/A	`http`	`$.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.

Trigger Authentication#

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

To use the API you will need your DEAR Account ID and API Application key. These can be created on the API setup page inside DEAR Inventory application.

About DEAR Systems#

DEAR Inventory is a comprehensive inventory control application positioned as a complete back end management system with product planning, cost and development, manufacturing, sales, shipping and payment features.

Action#

Create Note on Evernote

Description:Creates a new note in Evernote. [See the documentation](https://dev.evernote.com/doc/reference/NoteStore.html#Fn_NoteStore_createNote)

Version:0.0.1

Key:evernote-create-note

View on GitHub

Action Code#

import { ConfigurationError } from "@pipedream/platform";
import { parseObject } from "../../common/utils.mjs";
import evernote from "../../evernote.app.mjs";

export default {
  key: "evernote-create-note",
  name: "Create Note",
  description: "Creates a new note in Evernote. [See the documentation](https://dev.evernote.com/doc/reference/NoteStore.html#Fn_NoteStore_createNote)",
  version: "0.0.1",
  type: "action",
  props: {
    evernote,
    title: {
      type: "string",
      label: "Title",
      description: "The subject of the note. Can't begin or end with a space.",
    },
    content: {
      type: "string",
      label: "Content",
      description: "The XHTML block that makes up the note. This is the canonical form of the note's contents, so will include abstract Evernote tags for internal resource references. A client may create a separate transformed version of this content for internal presentation, but the same canonical bytes should be used for transmission and comparison unless the user chooses to modify their content.",
      default: "<?xml version=\"1.0\" encoding=\"UTF-8\"?><!DOCTYPE en-note SYSTEM \"http://xml.evernote.com/pub/enml2.dtd\"><en-note></en-note>",
      optional: true,
    },
    active: {
      type: "boolean",
      label: "Active",
      description: "If the note is available for normal actions and viewing",
      optional: true,
    },
    notebookGuid: {
      propDefinition: [
        evernote,
        "notebookGuid",
      ],
      optional: true,
    },
    tagGuids: {
      propDefinition: [
        evernote,
        "tagGuids",
      ],
      optional: true,
    },
    attributes: {
      type: "object",
      label: "Attributes",
      description: "A list of the attributes for this note. [See the documentation](https://dev.evernote.com/doc/reference/Types.html#Struct_NoteAttributes) for further details.",
      optional: true,
    },
    noUpdateTitle: {
      type: "boolean",
      label: "No Update Title",
      description: "The client may not update the note's title.",
      optional: true,
    },
    noUpdateContent: {
      type: "boolean",
      label: "No Update Content",
      description: "The client may not update the note's content. Content includes `content` and `resources`, as well as the related fields `contentHash` and `contentLength`.",
      optional: true,
    },
    noUpdateEmail: {
      type: "boolean",
      label: "No Update Email",
      description: "The client may not email the note.",
      optional: true,
    },
    noUpdateShare: {
      type: "boolean",
      label: "No Update Share",
      description: "The client may not share the note with specific recipients.",
      optional: true,
    },
    noUpdateSharePublicly: {
      type: "boolean",
      label: "No Update Share Publicly",
      description: "The client may not make the note public.",
      optional: true,
    },
  },
  async run({ $ }) {
    try {
      const note = await this.evernote.createNote({
        title: this.title,
        content: this.content,
        active: this.active,
        notebookGuid: this.notebookGuid,
        tagGuids: this.tagGuids,
        resources: this.resources,
        attributes: parseObject(this.attributes),
        restrictions: {
          noUpdateTitle: this.noUpdateTitle,
          noUpdateContent: this.noUpdateContent,
          noUpdateEmail: this.noUpdateEmail,
          noUpdateShare: this.noUpdateShare,
          noUpdateSharePublicly: this.noUpdateSharePublicly,
        },
      });

      $.export("$summary", `Created note "${note.title}" with ID ${note.guid}`);
      return note;
    } catch ({ parameter }) {
      throw new ConfigurationError(parameter);
    }
  },
};

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
Evernote	`evernote`	`app`	This component uses the Evernote app.
Title	`title`	`string`	The subject of the note. Can't begin or end with a space.
Content	`content`	`string`	The XHTML block that makes up the note. This is the canonical form of the note's contents, so will include abstract Evernote tags for internal resource references. A client may create a separate transformed version of this content for internal presentation, but the same canonical bytes should be used for transmission and comparison unless the user chooses to modify their content.
Active	`active`	`boolean`	If the note is available for normal actions and viewing
Notebook ID	`notebookGuid`	`string`	Select a value from the drop down menu.
Tag IDs	`tagGuids`	`string[]`	Select a value from the drop down menu.
Attributes	`attributes`	`object`	A list of the attributes for this note. See the documentation for further details.
No Update Title	`noUpdateTitle`	`boolean`	The client may not update the note's title.
No Update Content	`noUpdateContent`	`boolean`	The client may not update the note's content. Content includes `content` and `resources`, as well as the related fields `contentHash` and `contentLength`.
No Update Email	`noUpdateEmail`	`boolean`	The client may not email the note.
No Update Share	`noUpdateShare`	`boolean`	The client may not share the note with specific recipients.
No Update Share Publicly	`noUpdateSharePublicly`	`boolean`	The client may not make the note public.