Choose Best Completion with Cohere API on New Outbound Message (Instant) from Salesforce (REST API) API

Pipedream makes it easy to connect APIs for Cohere, Salesforce (REST API) and 2,000+ other apps remarkably fast.

Trigger workflow on

New Outbound Message (Instant) from the Salesforce (REST API) API

Next, do this

Choose Best Completion with the Cohere API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

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

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a Salesforce (REST API) trigger and Cohere action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Outbound Message (Instant) trigger
1. Connect your Salesforce (REST API) account
Configure the Choose Best Completion action
1. Connect your Cohere account
2. Configure Prompt
3. Optional- Select a Model
4. Optional- Configure Number of generations
5. Optional- Configure Max Tokens
6. Optional- Configure Preset
7. Optional- Configure Temperature
8. Optional- Configure K
9. Optional- Configure P
10. Optional- Configure Frequency Penalty
11. Optional- Configure End Sequences
12. Optional- Configure Stop Sequences
13. Optional- Select a Return Likelihoods
14. Optional- Configure Logit Bias
15. Optional- Select a Truncate
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 Outbound Message (Instant) on Salesforce (REST API)

Description:Emit new event when a new outbound message is received in Salesforce. See Salesforce's guide on setting up [Outbound Messaging](https://sforce.co/3JbZJom). Set the Outbound Message's Endpoint URL to the endpoint of the created source. The "Send Session ID" option must be enabled for validating outbound messages from Salesforce.

Version:0.1.6

Key:salesforce_rest_api-new-outbound-message

View on GitHub

Salesforce (REST API) Overview#

The Salesforce (REST API) provides a powerful platform for creating and managing customer relationships with a wide array of features like data manipulation, querying, and complex automation. With Pipedream's serverless execution, you can create workflows that automate your sales processes, sync data with other platforms, enhance customer engagement, and trigger actions based on specific events. Dive into Salesforce data, streamline lead management, track customer interactions, and push or pull data to or from Salesforce seamlessly.

Trigger Code#

import { XMLParser } from "fast-xml-parser";
import salesforce from "../../salesforce_rest_api.app.mjs";

export default {
  type: "source",
  name: "New Outbound Message (Instant)",
  key: "salesforce_rest_api-new-outbound-message",
  description: "Emit new event when a new outbound message is received in Salesforce. See Salesforce's guide on setting up [Outbound Messaging](https://sforce.co/3JbZJom). Set the Outbound Message's Endpoint URL to the endpoint of the created source. The \"Send Session ID\" option must be enabled for validating outbound messages from Salesforce.",
  version: "0.1.6",
  dedupe: "unique",
  props: {
    db: "$.service.db",
    // eslint-disable-next-line pipedream/props-label,pipedream/props-description
    http: {
      type: "$.interface.http",
      customResponse: true,
    },
    salesforce,
  },
  methods: {
    _unwrapMessage(message) {
      const parser = new XMLParser({
        removeNSPrefix: true,
      });
      const obj = parser.parse(message);
      const notifications = obj["Envelope"]["Body"].notifications;
      return notifications;
    },
    _sendHttpResponse(successValue = true, status) {
      // eslint-disable-next-line multiline-ternary
      status = status ?? (successValue ? 200 : 400);
      this.http.respond({
        status,
        body: `
          <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
          xmlns:out="http://soap.sforce.com/2005/09/outbound">
            <soapenv:Header/>
            <soapenv:Body>
              <out:notificationsResponse>
                <out:Ack>${successValue}</out:Ack>
              </out:notificationsResponse>
            </soapenv:Body>
          </soapenv:Envelope>
        `,
        headers: {
          "content-type": "text/xml",
        },
      });
    },
    async _isValidSessionId(sessionId) {
      try {
        const data = await this.salesforce.getUserInfo(sessionId);
        return Boolean(data);
      } catch (err) {
        console.log("Error validating SessionId:", err);
        return false;
      }
    },
    async _isValidSource(data) {
      const { SessionId: sessionId } = data;
      if (!sessionId) {
        throw new Error("The outbound message is missing a Session ID. Please configure the outbound message to send Session ID to validate the webhook source.");
      }

      return this._isValidSessionId(sessionId);
    },
    generateMeta(data) {
      const {
        ActionId: actionId,
        Notification: { Id: eventId },
      } = data;
      const id = `${eventId}-${actionId}`;
      const summary = JSON.stringify(data);
      const ts = Date.now();
      return {
        id,
        summary,
        ts,
      };
    },
  },
  async run(event) {
    const { bodyRaw } = event;
    this._sendHttpResponse(true);
    const data = this._unwrapMessage(bodyRaw);
    if (!(await this._isValidSource(data))) {
      console.log("Skipping event from unrecognized source");
      return;
    }

    let notifications = data.Notification;
    if (!Array.isArray(notifications)) {
      notifications = [
        data.Notification,
      ];
    }

    notifications.forEach((n) => {
      const notification = Object.assign(data, {
        Notification: n,
      });
      this.$emit(notification, this.generateMeta(notification));
    });
  },
};

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	`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.
Salesforce (REST API)	`salesforce`	`app`	This component uses the Salesforce (REST API) app.

Trigger Authentication#

Salesforce (REST API) uses OAuth authentication. When you connect your Salesforce (REST API) account, Pipedream will open a popup window where you can sign into Salesforce (REST API) and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Salesforce (REST API) API.

Pipedream requests the following authorization scopes when you connect your account:

About Salesforce (REST API)#

Web services API for interacting with Salesforce

Action#

Choose Best Completion on Cohere

Description:This action chooses the best completion conditioned on a given examples. [See the docs here](https://docs.cohere.ai/reference/generate)

Version:0.0.2

Key:cohere_platform-choose-best-completion

View on GitHub

Cohere Overview#

The Cohere API enables the development of apps with advanced natural language understanding capabilities. Utilizing machine learning, it can help with tasks like text generation, summarization, sentiment analysis, and more. On Pipedream, you can seamlessly integrate Cohere's features into serverless workflows, triggering actions based on text input, processing large volumes of data, or even enhancing chatbots with more human-like responses.

Action Code#

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

export default {
  ...common,
  key: "cohere_platform-choose-best-completion",
  name: "Choose Best Completion",
  version: "0.0.2",
  description: "This action chooses the best completion conditioned on a given examples. [See the docs here](https://docs.cohere.ai/reference/generate)",
  type: "action",
  props: {
    ...common.props,
    prompt: {
      propDefinition: [
        common.props.coherePlatform,
        "prompt",
      ],
      type: "string[]",
    },
  },
  methods: {
    ...common.methods,
    prepareAdditionalData({ prompt }) {
      return {
        prompt: prompt.toString(),
      };
    },
  },
};

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
Cohere	`coherePlatform`	`app`	This component uses the Cohere app.
Prompt	`prompt`	`string[]`	Represents the prompt or text to be completed. Trailing whitespaces will be trimmed. If your use case requires trailing whitespaces, please contact ivan@cohere.ai.
Model	`model`	`string`	Select a value from the drop down menu:`mediumxlarge`
Number of generations	`numGenerations`	`integer`	Defaults to 1, min value of 1, max value of 5. Denotes the maximum number of generations that will be returned.
Max Tokens	`maxTokens`	`integer`	Denotes the number of tokens to predict per generation, defaults to 20. See BPE Tokens for more details. Can only be set to `0` if `return_likelihoods` is set to `ALL` to get the likelihood of the prompt.
Preset	`preset`	`string`	The ID of a custom playground preset. You can create presets in the playground. If you use a preset, all other parameters become optional, and any included parameters will override the preset's parameters.
Temperature	`temperature`	`string`	Defaults to `0.75`, min value of `0.0`, max value of `5.0`. A non-negative float that tunes the degree of randomness in generation. Lower temperatures mean less random generations. See Temperature for more details.
K	`k`	`integer`	Defaults to `0`(disabled), which is the minimum. Maximum value is `500`. Ensures only the top `k` most likely tokens are considered for generation at each step.
P	`p`	`string`	Defaults to `0.75`. Set to `1.0` or `0` to disable. If set to a probability `0.0 < p < 1.0`, it ensures that only the most likely tokens, with total probability mass of `p`, are considered for generation at each step. If both `k` and `p` are enabled, `p` acts after `k`.
Frequency Penalty	`frequencyPenalty`	`string`	Defaults to `0.0`, min value of `0.0`, max value of `1.0`. Can be used to reduce repetitiveness of generated tokens. Similar to `frequency_penalty`, except that this penalty is applied equally to all tokens that have already appeared, regardless of their exact frequencies.
End Sequences	`endSequences`	`string[]`	The generated text will be cut at the beginning of the earliest occurence of an end sequence. The sequence will be excluded from the text.
Stop Sequences	`stopSequences`	`string[]`	The generated text will be cut at the end of the earliest occurence of a stop sequence. The sequence will be included the text.
Return Likelihoods	`returnLikelihoods`	`string`	Select a value from the drop down menu:`GENERATIONALLNONE`
Logit Bias	`logitBias`	`object`	Used to prevent the model from generating unwanted tokens or to incentivize it to include desired tokens. The format is `{token_id: bias}` where bias is a float between `-10` and `10`. Tokens can be obtained from text using Tokenize. For example, if the value `{'11': -10}` is provided, the model will be very unlikely to include the token 11 (`" "`, the newline character) anywhere in the generated text. In contrast `{'11': 10}` will result in generations that nearly only contain that token. Values between -10 and 10 will proportionally affect the likelihood of the token appearing in the generated text. Note: logit bias may not be supported for all custom models.
Truncate	`truncate`	`string`	Select a value from the drop down menu:`NONESTARTEND`

Action Authentication#

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

Generate and copy your API key from your Cohere Platform dashboard.

About Cohere#

Making NLP part of every developer's toolkit. Harness the power of language understanding. Join the developers and businesses who are using Cohere to generate, categorize and organize text at a scale that was previously unimaginable.

More Ways to Connect Cohere + Salesforce (REST API)#

Other Popular Integrations#

Choose Best Completion with Cohere API on New Object (of Selectable Type) from Salesforce (REST API) API

Salesforce (REST API) + Cohere

Choose Best Completion with Cohere API on New Outbound Message (Instant) from Salesforce (REST API) API

Pipedream makes it easy to connect APIs for Cohere, Salesforce (REST API) and 2,000+ other apps remarkably fast.

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

Developers ♥ Pipedream

1-24of2,000+apps by most popular

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