Salesforce Chatter search feed

Searches for feeds in the Authorizing user's Salesforce Chatter network.

Note: This is an external action and may execute on servers running outside your data center Centralized locations used to house servers used by Nintex for remote storage, processing, or distribution of data. Nintex has a number of regional data centers available for Nintex for Office 365. For information about Nintex data centers and where your data center is located, contact your Nintex account or territory manager. region. Before implementing, consider performance and regional concerns where digital boundaries are an issue. For more information, see In-tenant and external actions.

Action settings

Do one of the following to open the Action configuration window:

  • Double-click the action.
  • Click on the action and then click Configure.

See Action configuration window for more information.

Field Description

Username

Specify the Salesforce username.

Password

Specify the Salesforce password.

Security token

Specify the Salesforce security token.

Note: For more information on security tokens, refer to the following topic in Salesforce online help: "Resetting Your Security Token."

Search query

Specify the string to search. The search string must contain at least two characters, not including any wildcards and limited to 100 characters. Wildcards include the asterisk (*) and question mark (!), used as follows.

  • Asterisks (*) match zero or more characters at the middle or end (not the beginning) of your search term. For example, a search for john* finds items that start with john, such as, john, johnson, or johnny. A search for mi* meyers finds items with mike meyers or michael meyers.
  • Question marks (?) match only one character in the middle or end (not the beginning) of your search term. For example, a search for jo?n finds items with the term john or joan but not jon or johan.
Maximum results

Specify the maximum results to return.

Default value: 25. Valid values: 1-100. Default value is used if invalid value is specified.

Time zone

Specify the time zone to use for the dates.

Default value: UTC.
Dates

Specify a collection or dictionary variable to store the dates the feeds are posted in the specified timezone.
Feed type

Specify a collection or dictionary variable to store the feed types.
IDs

Specify a collection or dictionary variable to store the IDs of the feeds.
Information

Specify a collection or dictionary variable to store the feeds' text. The information includes who made the post, the type of feed and the recipient of the post. Examples of information according to feed type are below:

ContentPost:

  • Post to self: "User1 uploaded a file 'MyFile.doc' with the message "This is my message"."
  • Post to user: "User1 uploaded a file 'MyFile.doc' to User2 with the message "This is my message"."
  • Post to group: "User1 uploaded a file 'MyFile.doc' to 'MyGroup' group with the message "This is my message"."

LinkPost:

  • Post to self: "User1 posted a link 'My Link' (URL: http://www.nintex.com) with the message "This is my message"."
  • Post to user: "User1 posted a link 'My Link' (URL: http://www.nintex.com) to User2 with the message "This is my message"."
  • Post to group: "User1 posted a link 'My Link' (URL: http://www.nintex.com) to 'MyGroup' group with the message "This is my message"."

PollPost:

  • Post to self: "User1 posted a message 'This is my message'."
  • Post to user: "User1 posted a message 'This is my message' to User2."
  • Post to group: "User1 posted 'This is my message.' to 'MyGroup' group."

TextPost:

  • Post to self: "User1 posted a poll 'Which movie do you want to watch at nintex?'."
  • Post to user: "User1 posted a poll 'Which movie do you want to watch at nintex?' to User2."
  • Post to group: "User1 posted a poll 'Which movie do you want to watch at nintex?' to 'MyGroup' group."
URLs

Specify a collection or dictionary variable to store the feeds' web URLs.
Result count

Specify a numeric variable to store the number of results retrieved.
For more information about how to use Lookups in configuration fields, see Lookups in action configuration fields.