{"id":20745393,"url":"https://github.com/elasticio/salesforce-component","last_synced_at":"2025-04-24T06:13:53.098Z","repository":{"id":36842641,"uuid":"41149571","full_name":"elasticio/salesforce-component","owner":"elasticio","description":"elastic.io component that connects to Salesforce API (node.js)","archived":false,"fork":false,"pushed_at":"2022-12-07T17:35:34.000Z","size":990,"stargazers_count":3,"open_issues_count":31,"forks_count":5,"subscribers_count":16,"default_branch":"master","last_synced_at":"2025-04-24T06:13:46.393Z","etag":null,"topics":["eio-component"],"latest_commit_sha":null,"homepage":null,"language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/elasticio.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2015-08-21T10:11:13.000Z","updated_at":"2022-05-12T22:27:50.000Z","dependencies_parsed_at":"2023-01-17T05:38:24.229Z","dependency_job_id":null,"html_url":"https://github.com/elasticio/salesforce-component","commit_stats":null,"previous_names":[],"tags_count":1,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/elasticio%2Fsalesforce-component","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/elasticio%2Fsalesforce-component/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/elasticio%2Fsalesforce-component/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/elasticio%2Fsalesforce-component/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/elasticio","download_url":"https://codeload.github.com/elasticio/salesforce-component/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":250573356,"owners_count":21452352,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["eio-component"],"created_at":"2024-11-17T07:20:15.168Z","updated_at":"2025-04-24T06:13:53.074Z","avatar_url":"https://github.com/elasticio.png","language":"JavaScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# salesforce-component\n\n# DEPRECATED COMPONENT. USE https://github.com/elasticio/salesforce-component-v2 INSTEAD\n\n## Description\n[elastic.io](http://www.elastic.io;) iPaaS component that connects to Salesforce API\n\n### Purpose\nSalesforce component is designed for Salesforce API integration.\n\n###  Completeness Matrix\n![Salesforse-component Completeness Matrix](https://user-images.githubusercontent.com/36419533/75436046-9a5ef880-595c-11ea-838f-32660c119972.png)\n\n[Salesforse-component Completeness Matrix](https://docs.google.com/spreadsheets/d/1_4vvDLdQeXqs3c8OxFYE80CvpeSC8e3Wmwl1dcEGO2Q/edit?usp=sharing)\n\n\n### API version\nThe component uses Salesforce - API Version 45.0, except:\n- Deprecated Actions and Triggers - API Version 25.0\n\n### Authentication\nAuthentication occurs via OAuth 2.0.\nIn the component repository you need to specify OAuth Client credentials as environment variables:\n- ```OAUTH_CLIENT_ID``` - your OAuth client key\n- ```OAUTH_CLIENT_SECRET``` - your OAuth client secret\n\n## Create new App in Salesforce\n\nIn order to make OAuth work, you need a new App in your Salesforce. During app creation process you will be asked to specify\nthe callback URL, to process OAuth authentication via elastic.io platform your callback URL should be\n\n```https://your-tenant.elastic.io/callback/oauth2```\n\nMore information you can find [here](https://help.salesforce.com/apex/HTViewHelpDoc?id=connected_app_create.htm)\n\n## Credentials\n\nDuring credentials creation you would need to:\n- choose ``Environment``\n- enter ``Username`` and ``Password`` in a pop-up window after click on ``Authenticate`` button.\n- verify and save your new credentials.\n### Limitations\nAccording to [Salesforce documentation](https://help.salesforce.com/articleView?id=remoteaccess_request_manage.htm\u0026type=5)\n\n`Each connected app allows five unique approvals per user. When a sixth approval is made, the oldest approval is revoked.`\n\nYou can get error `refresh token has been expired` if the same user account was authenticated with same OAuth Application (OAuth Client) more than 4 times. This is feature of the Salesforce platform that automatically invalidates the oldest refresh_token as soon as a number of given refresh tokens for an individual user account exceeds 4.\n\n## Actions\n### Query\nExecuting a SOQL Query that may return many objects. Each resulting object is emitted one-by-one. Use the Salesforce Object Query Language (SOQL) to search your organization’s Salesforce data for specific information. SOQL is similar to the SELECT statement in the widely used Structured Query Language (SQL) but is designed specifically for Salesforce data. This action allows you to interact with your data using SOQL.\nEmpty object will be returned, if query doesn't find any data.\n\n#### Input fields description\n* **Include deleted** - checkbox, if checked - deleted records will be included into the result list.\n\n#### Input fields description\n* **Optional batch size** - A positive integer specifying batch size. If no batch size is specified then results of the query will be emitted one-by-one, otherwise, query results will be emitted in an array of maximum batch size.\n* **Allow all results to be returned in a set** - checkbox which allows emitting query results in a single array. `Optional batch size` option is ignored in this case.\n* **SOQL Query** - Input field where you should type the SOQL query. E.g. `\"SELECT ID, Name from Contact where Name like 'John Smi%'\"`\n* **Max Fetch Count** - limit for a number of messages that can be fetched. 1,000 is the default value when the variable is not set.\n\n### Create Object\nCreates a new Selected Object.\nAction creates a single object. Input metadata is fetched dynamically from your Salesforce account. Output metadata is the same as input metadata, so you may expect all fields that you mapped as input to be returned as output.\n\nNote:\nIn case of an **Attachment** object type you should specify `Body` in base64 encoding. `ParentId` is a Salesforce ID of an object (Account, Lead, Contact) which an attachment is going to be attached to.\n\n#### Input fields description\n* **Object** - Input field where you should choose the object type, which you want to find. E.g. `Account`\n* **Utilize data attachment from previous step (for objects with a binary field)** - a checkbox, if it is checked and an input message contains an attachment and specified object has a binary field (type of base64) then the input data is put into object's binary field. In this case any data specified for the binary field in the data mapper is discarded.\n\nThis action will automatically retrieve all existing fields of chosen object type that available on your Salesforce organization\n\n#### Limitations\nWhen **Utilize data attachment from previous step (for objects with a binary field)** is checked and this action is used with Local Agent error would be thrown: 'getaddrinfo ENOTFOUND steward-service.platform.svc.cluster.local steward-service.platform.svc.cluster.local:8200'\n\n### Delete Object (at most 1)\nDeletes an object by a selected field. One can filter by either unique fields or all fields of that sobject. Input metadata is fetched dynamically from your Salesforce account.\n\n#### Input field description\n* **Object** - dropdown list where you should choose the object type, which you want to find. E.g. `Account`.\n* **Type Of Search** -  dropdown list with two values: `Unique Fields` and `All Fields`.\n* **Lookup by field** - dropdown list with all fields on the selected object, if on *Type Of Search* is chosen `All Fields`, or with all fields on the selected object where `type` is `id` or `unique` is `true` , if on *Type Of Search* is chosen `Unique Fields` then all searchable fields both custom and standard will be available for selection.\n\nResult is an object with 3 fields.\n* **id** - `string`, salesforce object id\n* **success** - `boolean`, if operation was successful `true`\n* **errors** - `array`, if operation fails, it will contain description of errors\n\n#### Metadata description\nMetadata for each particular `Object type` + `Lookup by field` is generating dynamically.\n\n### Upsert Object\nCreates or Updates Selected Object.\nAction creates a single object. Input metadata is fetched dynamically from your Salesforce account. Output metadata is the same as input metadata, so you may expect all fields that you mapped as input to be returned as output.\n\n#### Input field description\n* **Object** - Input field where you should choose the object type, which you want to find. E.g. `Account`\n* **Optional Upsert field** - Input field where you should specify the ExternalID name field. E.g. `ExtId__c`.\n* **Utilize data attachment from previous step (for objects with a binary field)** - a checkbox, if it is checked and an input message contains an attachment and specified object has a binary field (type of base64) then the input data is put into object's binary field. In this case any data specified for the binary field in the data mapper is discarded.\n\nYou should specify **external** or **internal Id** for making some updates in salesforce object.\nIf you want to create new Object you should always specify **Optional Upsert field** and value of ExternalId in input body structure.\n\n#### Limitations\nWhen **Utilize data attachment from previous step (for objects with a binary field)** is checked and this action is used with Local Agent error would be thrown: 'getaddrinfo ENOTFOUND steward-service.platform.svc.cluster.local steward-service.platform.svc.cluster.local:8200'\n\n### Lookup Object (at most 1)\nLookup an object by a selected field.\nAction creates a single object. Input metadata is fetched dynamically from your Salesforce account. Output metadata is the same as input metadata, so you may expect all fields that you mapped as input to be returned as output.\n\n#### Input field description\n* **Object** - Dropdown list displaying all searchable object types. Select one type to query, e.g. `Account`.\n* **Type Of Search** - Dropdown list with two values: `Unique Fields` and `All Fields`.\n* **Lookup by field** - Dropdown list with all fields on the selected object if the *Type Of Search* is `All Fields`. If the *Type Of Search* is `Unique Fields`, the dropdown lists instead all fields on the selected object where `type` is `id` or `unique` is `true`.\n* **Include linked objects** - Multiselect dropdown list with all the related child and parent objects of the selected object type. List entries are given as `Object Name/Reference To (Relationship Name)`. Select one or more related objects, which will be join queried and included in the response from your Salesforce Organization. Please see the **Limitations** section below for use case advisories.\n* **Allow zero results** - Checkbox. If checked and nothing is found in your Salesforce Organization, an empty object will be returned. If not checked and nothing is found, the action will throw an error.\n* **Pass binary data to the next component (if found object has it)** - Checkbox. If it is checked and the found object record has a binary field (primitive type `base64`), then its data will be passed to the next component as a binary attachment.\n* **Enable Cache Usage** - Flag to enable cache usage.\n\n#### Metadata description\n\nMetadata contains one field whose name, type and mandatoriness are generated according to the value of the configuration fields *Lookup by field* and *Allow criteria to be omitted*.\n\n#### Limitations\nWhen a binary field (primitive type `base64`, e.g. Documents, Attachments, etc) is selected on **Include linked objects**, an error will be thrown: 'MALFORMED_QUERY: Binary fields cannot be selected in join queries. Instead of querying objects with binary fields as linked objects (such as children Attachments), try querying them directly.' There is also a limit to the number of linked objects that you can query at once - beyond two or three, depending on the number of fields in the linked objects, Salesforce could potentially return a Status Code 431 or 414 error, meaning the query is too long. Finally, due to a bug with multiselect dropdowns, it is recommended to deselect all of the elements in this field before you change your selection in the *Object* dropdown list.\n\nWhen **Pass binary data to the next component (if found object has it)** is checked and this action is used with Local Agent, an error will be thrown: 'getaddrinfo ENOTFOUND steward-service.platform.svc.cluster.local steward-service.platform.svc.cluster.local:8200'\n\n#### Note\nAction has caching mechanism. By default action stores last 10 request-response pairs for 10 min duration.\nThis parameters can be changed by setting environment variables:\n* **HASH_LIMIT_TIME** - Hash expiration time in milis\n* **HASH_LIMIT_ELEMENTS** - Hash size number limit\n\n### Lookup Objects\nLookup a list of objects satisfying specified criteria.\n\n#### Input field description\n* **Object** - dropdown list where you should choose the object type, which you want to find. E.g. `Account`.\n* **Include deleted** - checkbox, if checked - deleted records will be included into the result list.\n* **Output method** - dropdown list with following values: \"Emit all\", \"Emit page\", \"Emit individually\".\n* **Number of search terms** - text field to specify a number of search terms (positive integer number [1-99] or 0).\n* **Enable Cache Usage** - Flag to enable cache usage.\n* **Max Fetch Count** - limit for a number of messages that can be fetched. 1,000 is the default value when the variable is not set.\n\n#### Note\nAction has caching mechanism. By default action stores last 10 request-response pairs for 10 min duration.\nThis parameters can be changed by setting environment variables:\n* **HASH_LIMIT_TIME** - Hash expiration time in milis\n* **HASH_LIMIT_ELEMENTS** - Hash size number limit\n\n#### Metadata description\n\nDepending on the the configuration field *Output method* the input metadata can contain different fields:\n*Output method* - \"Emit page\":\nField \"Page size\" - optional positive integer that defaults to 1000;\nField \"Page number\" - required non-negative integer (starts with 0, default value 0);\n\n*Output method* - \"Emit all\":\nField \"Maximum number of records\" - optional positive integer (default value 1000);\n\n*Output method* - \"Emit individually\":\nField \"Maximum number of records\" - optional positive integer (default value 10000);\n\nNote that the number of records the component emits may affect the performance of the platform/component.\n\nGroups of fields for each search term go next:\n\nField \"Field name\" - string represents object's field (a list of allowed values is available);\nField \"Field value\" - string represents value for selected field;\nField \"Condition\" - one of the following: \"=\", \"!=\", \"\u003c\", \"\u003c=\", \"\u003e\", \"\u003e=\", \"LIKE\", \"IN\", \"NOT IN\";\n\nBetween each two term's group of fields:\n\nField \"Logical operator\" - one of the following: \"AND\", \"OR\";\n\nOutput data is an object, with a field \"results\" that is an array of objects.\n\n### Bulk Create/Update/Delete/Upsert\nBulk API provides a simple interface for quickly loading large amounts of data from CSV file into Salesforce (up to 10'000 records).\nAction takes a CSV file from the attachment as an input. CSV file format is described in the [Salesforce documentatio](https://developer.salesforce.com/docs/atlas.en-us.api_bulk_v2.meta/api_bulk_v2/datafiles.htm)\n\n#### Input field description\n* **Operation** - dropdown list with 3 supported operations: `Create`, `Update` and `Delete`.\n* **Object** - dropdown list where you should choose the object type to perform bulk operation. E.g. `Case`.\n* **Timeout** - maximum time to wait until the server completes a bulk operation (default: `600` sec).\n\n#### Metadata description\n* **External ID Field** - a name of the External ID field for `Upsert` operation. E.g. `my_external_id__c`\n\nResult is an object with a property **result**: `array`. It contains objects with 3 fields.\n* **id** - `string`, salesforce object id\n* **success** - `boolean`, if operation was successful `true`\n* **errors** - `array`, if operation failed contains description of errors\n\n#### Limitations\n* No errors thrown in case of failed Object Create/Update/Delete/Upsert (`\"success\": \"false\"`).\n* Object ID is needed for Update and Delete.\n* External ID is needed for Upsert.\n* Salesforce processes up to 10'000 records from the input CSV file.\n\n\n### Bulk Query\nFetches records to a CSV file.\n\n#### Input field description\n* **SOQL Query** - Input field where you should type the SOQL query. E.g. `\"SELECT ID, Name from Contact where Name like 'John Smi%'\"`\n\nResult is a CSV file in the attachment.\n\n\n### Lookup Object (deprecated)\nLookup an object by a selected field.\nAction creates a single object. Input metadata is fetched dynamically from your Salesforce account. Output metadata is the same as input metadata, so you may expect all fields that you mapped as input to be returned as output.\n\n#### Input field description\n* **Optional batch size** - A positive integer specifying batch size. If no batch size is specified then results of the query will be emitted one-by-one, otherwise, query results will be emitted in an array of maximum batch size.\n* **Object** - Input field where you should choose the object type, which you want to find. E.g. `Account`\n* **Lookup field** - Input field where you should choose the lookup field which you want to use for result filtering. E.g. `Id`.\n* **Max Fetch Count** - limit for a number of messages that can be fetched. 1,000 is the default value when the variable is not set.\n\n```For now, you can specify all unique, lookup, ExternalID/Id fields. ```\n\n##### Execution result handling\n|Condition | Execution result |\n|----------|------------------|\n|Lookup failed - we were not able to find any parent object. |Lookup action emits a single message with an empty body.|\n|Lookup found a single object, e.g. we were able to identify a parent Account to the Contact|A single message will be emitted, found object will be a body of the message|\n|Lookup found multiple objects (that may happen when a lookup is made by non-unique field) | Each found object will be emitted with the separate message|\n\n### New Account `(deprecated)`\nCreates a new Account.\nAction creates a single object. Input metadata is fetched dynamically from your Salesforce account. Output metadata is the same as input metadata, so you may expect all fields that you mapped as input to be returned as output.\n\n#### Input fields description\nThis action will automatically retrieve all existing fields of `Account` object type that available on your Salesforce organization.\n\nAction is `deprecated`. You can use [Create Object](#create-object) action instead.\n\n### New Case `(deprecated)`\nCreates a new Case.\nAction creates a single object. Input metadata is fetched dynamically from your Salesforce account. Output metadata is the same as input metadata, so you may expect all fields that you mapped as input to be returned as output.\n\n#### Input fields description\nThis action will automatically retrieve all existing fields of `Case` object type that available on your Salesforce organization\n\nAction is `deprecated`. You can use [Create Object](#create-object) action instead.\n\n### New Contact `(deprecated)`\nCreates a new Contact.\nAction creates a single object. Input metadata is fetched dynamically from your Salesforce account. Output metadata is the same as input metadata, so you may expect all fields that you mapped as input to be returned as output.\n\n\n#### Input fields description\nThis action will automatically retrieve all existing fields of `Contact` object type that available on your Salesforce organization\n\nAction is `deprecated`. You can use [Create Object](#create-object) action instead.\n\n### New Event `(deprecated)`\nCreates a new Event.\nAction creates a single object. Input metadata is fetched dynamically from your Salesforce account. Output metadata is the same as input metadata, so you may expect all fields that you mapped as input to be returned as output.\n\n#### Input fields description\nThis action will automatically retrieve all existing fields of `Event` object type that available on your Salesforce organization\n\nAction is `deprecated`. You can use [Create Object](#create-object) action instead.\n\n### New Lead `(deprecated)`\nCreates a new Lead.\nAction creates a single object. Input metadata is fetched dynamically from your Salesforce account. Output metadata is the same as input metadata, so you may expect all fields that you mapped as input to be returned as output.\n\n#### Input fields description\nThis action will automatically retrieve all existing fields of `Lead` object type that available on your Salesforce organization\n\nAction is `deprecated`. You can use [Create Object](#create-object) action instead.\n\n### New Note `(deprecated)`\nCreates a new Note.\nAction creates a single object. Input metadata is fetched dynamically from your Salesforce account. Output metadata is the same as input metadata, so you may expect all fields that you mapped as input to be returned as output.\n\n#### Input fields description\nThis action will automatically retrieve all existing fields of `Note` object type that available on your Salesforce organization\n\nAction is `deprecated`. You can use [Create Object](#create-object) action instead.\n\n### New Task `(deprecated)`\nCreates a new Task.\nAction creates a single object. Input metadata is fetched dynamically from your Salesforce account. Output metadata is the same as input metadata, so you may expect all fields that you mapped as input to be returned as output.\n\n#### Input fields description\nThis action will automatically retrieve all existing fields of `Task` object type that available on your Salesforce organization\n\nAction is `deprecated`. You can use [Create Object](#create-object) action instead.\n\n## Triggers\n### Query\nContinuously runs the same SOQL Query and emits results one-by-one.\nUse the Salesforce Object Query Language (SOQL) to search your organization’s Salesforce data for specific information. SOQL is similar to the SELECT statement in the widely used Structured Query Language (SQL) but is designed specifically for Salesforce data. This action allows you to interact with your data using SOQL.\n\n#### List of Expected Config fields\n\n* **SOQL Query** - Input field for your SOQL Query\n* **Output method** - dropdown list with options: `Emit all` - all found records will be emitted in one array `records`, and `Emit individually` - each found object will be emitted individual. Optional field, defaults to: `Emit individually`.\n\nNOTE: Max possible fetch size is 2000 objects per execution.\n\n### Get New and Updated Objects Polling\nPolls existing and updated objects. You can select any custom or built-in object for your Salesforce instance.\n\n#### Input field description\n* **Object** - Input field where you should select the type of object which updates you want to get. E.g. `Account`;\n* **Start Time** - Indicates the beginning time to start polling from. Defaults to `1970-01-01T00:00:00.000Z`;\n* **End Time** - If provided, don’t fetch records modified after this time;\n* **Size of Polling Page** - Indicates the size of pages to be fetched. You can set positive integer, max `10 000`, defaults to `1000`;\n* **Process single page per execution** - You can select on of options (defaults to `yes`):\n   1. `yes` - if the number of changed records exceeds the maximum number of results in a page, wait until the next flow start to fetch the next page;\n   2. `no` - if the number of changed records exceeds the maximum number of results in a page, the next pages will fetching in the same execution.\n* **Include linked objects** - Multiselect dropdown list with all the related child and parent objects of the selected object type. List entries are given as `Object Name/Reference To (Relationship Name)`. Select one or more related objects, which will be join queried and included in the response from your Salesforce Organization. Please see the **Limitations** section below for use case advisories.\n* **Output method** - dropdown list with options: `Emit all` - all found records will be emitted in one array `records`, and `Emit individually` - each found object will be emitted individual. Optional field, defaults to: `Emit individually`.\n* **Max Fetch Count** - limit for a number of messages that can be fetched. 1,000 is the default value when the variable is not set.\nFor example, you have 234 “Contact” objects, 213 of them were changed from 2019-01-01.\nYou want to select all “Contacts” that were changed from 2019-01-01, set the page size to 100 and process single page per execution.\nFor you purpose you need to specify following fields:\n   * Object: `Contact`\n   * Start Time: `2019-01-01T00:00:00.000Z`\n   * Size of Polling Page: `100`\n   * Process single page per execution: `yes` (or leave this empty)\n![image](https://user-images.githubusercontent.com/16806832/55322499-30f11400-5485-11e9-81da-50518f76258c.png)\n\nAs a result, all contacts will be fetched in three calls of the trigger: two of them by 100 items, and the last one by 13.\nIf you select `no` in **Process single page per execution**, all 213 contacts will be fetched in one call of the trigger.\n\n#### Limitations\nWhen a binary field (primitive type `base64`, e.g. Documents, Attachments, etc) is selected on **Include linked objects**, an error will be thrown: 'MALFORMED_QUERY: Binary fields cannot be selected in join queries. Instead of querying objects with binary fields as linked objects (such as children Attachments), try querying them directly.' There is also a limit to the number of linked objects that you can query at once - beyond two or three, depending on the number of fields in the linked objects, Salesforce could potentially return a Status Code 431 or 414 error, meaning the query is too long. Finally, due to a bug with multiselect dropdowns, it is recommended to deselect all of the elements in this field before you change your selection in the *Object* dropdown list.\n\n### Subscribe to platform events (REALTIME FLOWS ONLY)\nThis trigger will subscribe for any platform Event using Salesforce streaming API.\n\n#### Input field description\n* **Event object name** - Input field where you should select the type of platform event which you want to subscribe E.g. `My platform event`\n\n#### How to create new custom Platform event Entity:\n`Setup --\u003e Integrations --\u003e Platform Events --\u003e New Platform Event`\n![Screenshot from 2019-03-11 11-51-10](https://user-images.githubusercontent.com/13310949/54114889-1088e900-43f4-11e9-8b49-3a8113b6577d.png)\n\nYou can find more detail information in the [Platform Events Intro Documentation](https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_intro.htm).\n#### Environment Variables\n\n1. `SALESFORCE_API_VERSION` - API version for not deprecated actions and triggers e.g(46.0), default value 45.0\n\n2. `LOG_LEVEL` - `trace` | `debug` | `info` | `warning` | `error` controls logger level\n\n#### Limitations:\nAt the moment this trigger can be used only for **\"Realtime\"** flows.\n\n### New Case `(deprecated)`\nPolls existing and updated Cases (fetches a maximum of 1000 objects per execution)\n\nTrigger is `deprecated`. You can use [Get New and Updated Objects Polling](#get-new-and-updated-objects-polling) action instead.\n\n### New Lead `(deprecated)`\nPolls existing and updated Leads (fetches a maximum of 1000 objects per execution)\n\nTrigger is `deprecated`. You can use [Get New and Updated Objects Polling](#get-new-and-updated-objects-polling) action instead.\n\n### New Contact `(deprecated)`\nPolls existing and updated Contacts (fetches a maximum of 1000 objects per execution)\n\nTrigger is `deprecated`. You can use [Get New and Updated Objects Polling](#get-new-and-updated-objects-polling) action instead.\n\n### New Account `(deprecated)`\nPolls existing and updated Accounts (fetches a maximum of 1000 objects per execution)\n\nTrigger is `deprecated`. You can use [Get New and Updated Objects Polling](#get-new-and-updated-objects-polling) action instead.\n\n### New Task `(deprecated)`\nPolls existing and updated Tasks (fetches a maximum of 1000 objects per execution)\n\nTrigger is `deprecated`. You can use [Get New and Updated Objects Polling](#get-new-and-updated-objects-polling) action instead.\n\n## Known limitations\nAttachments mechanism does not work with [Local Agent Installation](https://support.elastic.io/support/solutions/articles/14000076461-announcing-the-local-agent-)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Felasticio%2Fsalesforce-component","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Felasticio%2Fsalesforce-component","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Felasticio%2Fsalesforce-component/lists"}