Create Opportunity (Salesforce) v3.0.13 Help ​

Creates a new opportunity record in Salesforce.

How can I use the Step? ​

You can use the Step to automate adding new opportunity information to a Salesforce database. The Step lets you quickly and efficiently input opportunity data without manual entry, saving time and reducing errors. Additionally, it can be integrated with other systems or applications to streamline overall business processes.

How does the Step work? ​

You authorize the Step and input opportunity details such as name and associated account, amount, close date, description, and other relevant information. The Step takes these inputs and requests Salesforce API to create a new opportunity record with the specified details (see Output example).

Review the Salesforce documentation on Opportunities.

Prerequisites ​

Before you get started, you must do the following:

  • Obtain the Consumer Key and Consumer Secret of the Salesforce Connected App you want to authorize the Step with. For more information about creating and configuring a Connected App, see Create a Connected App documentation.

Authorization ​

To authorize the Step, you can inherit authorization from a previous Step, select existing authorization or create a new one.

Here are the steps to create a new Salesforce authorization:

  1. For Select authorization in the current Step, choose the Create a new authorization option from the dropdown.

  2. In the Add an authorization popup, do the following:

    • For Your Connected Apps, select an existing Connected App or click Add a new Connected App and provide the required details in a popup:

      • Name this Connected App: Connected App name.
      • Environment: Environment choice for the Connected App in Salesforce. Either production or sandbox.
      • Consumer Key: Consumer Key for Connected App in Salesforce (see Prerequisites).
      • Consumer Secret: Consumer Secret for Connected App in Salesforce (see Prerequisites).
      • Callback URL: OAuth 2.0 redirect URL. You must use it as Callback URL when creating Connected App on Salesforce.

    • Name your new authorization.

    • Choose where to save the authorization.

    • Authorize the Step by clicking Authorize now or pasting the authorization URL into a web browser.

Once the Step is authorized, all related settings are automatically updated, and you can continue with the Step settings.

Opportunity information ​

The fields for this section refer to Opportunity Fields in Salesforce and contain a range of information to help you track your pending and potential sales. Some fields may not be visible or editable, depending on field-level security settings.

The following fields are required:

  • Opportunity Name
  • Close Date
  • Stage

Advanced settings ​

You can use this section to configure the following parameter:

  • API version: The Salesforce API version for requests. The value must be in the format 50 or 50.0 and contain at least two characters. The default API version is 50, and the minimum supported version is 21.

Description information ​

In the Description field, you can briefly describe the opportunity.

Additional information ​

The inputs for this section are optional and refer to opportunity custom fields.

You can find more information about a particular custom field in your Salesforce account under Setup > Object Manager> Opportunity > Fields & Relationships.

Merge field settings ​

The Step returns the result as a JSON object and stores it in the Merge field variable. So you can use the retrieved data in subsequent Steps or other Flows.

Output example ​

The output depends on the development and settings you provide. It contains the record ID, success status, errors, and a data object with the fields of the opportunity record populated.

To learn more, see the following output example:

json
{
    "response": {
        "success": true,
        "id": "0061r00000wxRciAAE",
    },
    "data": {
        "AccountId": "0011r00001mvDY4AAM",
        "IsPrivate": true,
        "Name": "name",
        "Description": "This fields for Description",
        "StageName": "Prospecting",
        "Amount": "112345",
        "Probability": "99",
        "CloseDate": "2018-05-29T18:42:32.298Z",
        "Type": "Existing Customer - Upgrade",
        "NextStep": "Update_test",
        "LeadSource": "Phone Inquiry",
        "CampaignId": "7011r000001awTZAAY"
    }
}
{
    "response": {
        "success": true,
        "id": "0061r00000wxRciAAE",
    },
    "data": {
        "AccountId": "0011r00001mvDY4AAM",
        "IsPrivate": true,
        "Name": "name",
        "Description": "This fields for Description",
        "StageName": "Prospecting",
        "Amount": "112345",
        "Probability": "99",
        "CloseDate": "2018-05-29T18:42:32.298Z",
        "Type": "Existing Customer - Upgrade",
        "NextStep": "Update_test",
        "LeadSource": "Phone Inquiry",
        "CampaignId": "7011r000001awTZAAY"
    }
}

Error Handling ​

By default, the Handle error toggle is on, and the Step handles errors with a separate exit. If any error occurs during the Step execution, the Flow proceeds down the error exit.

If the Handle error toggle is disabled, the Step does not handle errors. In this case, if any error occurs during the Step execution, the Flow fails immediately after exceeding the Flow timeout. To prevent the Flow from being suspended and continue handling errors, you can place the Flow Error Handling Step before the main logic or your Flow.

Reporting ​

After the Step completes, it generates a report that includes its execution status and other details. You can customize the report by adjusting the Step's log level and adding tags.

Log level ​

By default, the Step's log level matches that of the Flow. You can change the Step's log level by selecting an appropriate option from the Log level dropdown.

Tags ​

Tags provide a way to classify and search for sessions based on their attributes. To create a new tag, specify its category, label, and value. You can then use tags to filter and group the sessions in the report.

Service dependencies ​

  • flow builder v2.28.3
  • event-manager v2.3.0
  • deployer v2.6.0
  • library v2.11.3
  • studio v2.64.1
  • authorizer 2 service v2.1.6
  • salesforce data provider

Release notes ​

v3.0.13

  • Add API version selection to the Step UI

v3.0.12

  • Update dropdowns behavior

v3.0.10

  • Set default value for dropdown fields

v3.0.9

  • Update Authorization Manager 1.2.9
  • Add the None option to dropdown
  • Update date handling

v3.0.8

  • Update UI tooltips
  • Update error handling
  • Remove extra data

v3.0.7

  • Implement Authorization Manager v 1.1.0
  • Remove the dynamicAll switch handling
  • Add Step migration

v3.0.4

  • Update Authorization Manager v1.0.5
  • Add dynamic instance_url

v3.0.3

  • Update Authorization Manager v1.0.4

v3.0.1

  • Update the toJSON function and wildcard logic with the new Merge field expression template