Handshook is a mobile CRM app that uses AI for scanning business card and event badges and features automated follow-ups and data enrichment.

Handshook

Limit to opportunities closed as either Won or Lost.

Select the object's field history you want to track. To use this trigger you must enable [track object field history](https://help.salesforce.com/s/articleView?id=sf.tracking_field_history_for_standard_objects.htm&type=5) in Salesforce.

Select an object to monitor for new or updated files.

Optionally select a specific record to monitor for files. If not selected, the trigger will watch all records of the selected object.

Select an object to use to monitor new records.

Pick the stage to watch the opportunity gets updated on.

Use for Salesforce objects with fewer than 104,000 records and where "Field updated to" is specified. View storage usage to see your record count. You can set up a Zap using the New Outbound Message trigger as a workaround if you are over the record limit.

Select an object to use to watch for changes.

Limit to opportunities that are in the selected stage after being updated.

Select an object to use to monitor updated records.

Choose how you want to build your SOQL query

Include records that have been moved to the Recycle Bin

If empty, we will search for the same value as the first search.

The **AND** operator searches for records that match both search fields; the **OR** operator searches for records that match at least one of the search fields. The default is OR.

Select the type of object to search. You can only search for multiple records of the same object type.

Specify how to return search results from Salesforce. It will be applied to each search value that is found.

Create a WHERE clause to define the criteria that Salesforce will use to find specific records using [Salesforce Object Query Language (SOQL)](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql.htm). Make sure to properly escape special characters in your query strings - see [SOQL documentation on escaping](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_select_quotedstringescapes.htm). [View examples](https://help.zapier.com/hc/en-us/articles/8496020846605-Tips-and-tricks-with-Salesforce-triggers-and-actions#use-the-find-object-by-query-search-0-4)

Create a WHERE clause to define the criteria that Salesforce will use to find specific records using Salesforce Object Query Language (SOQL). Make sure to properly escape special characters in your query strings - see [SOQL documentation on escaping](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql_select_quotedstringescapes.htm). [View examples](https://developer.salesforce.com/docs/atlas.en-us.soql_sosl.meta/soql_sosl/sforce_api_calls_soql.htm)

Select the type of Salesforce record you want to get attachments from.

Search for or select the record you want to get attachments from. If you cannot find the record you need, try refreshing the results after you have selected the Salesforce object in the previous field.

Select "Yes" to use active Salesforce assignment rules. Select "No" if you don not want to use assignment rules when creating this lead.

**Allow Duplicates:** Select "Yes" to permit the creation of duplicate records.
Be aware that this functionality depends on your Salesforce account's specific configurations and user permissions.

- Duplicate Rules must be set to allow duplicates for the relevant objects.
- Your user profile must have the necessary permissions to override duplicate settings.

For detailed guidance, refer to the [Salesforce Duplicate Management Documentation](https://help.salesforce.com/s/articleView?id=sales.duplicate_prevention_map_of_tasks.htm&type=5) or consult your Salesforce administrator.

Select the campaign to add the contact. If you cannot find the campaign you need, try refreshing the results.

If you cannot find the contact you need, try refreshing the results.

Select the content document ID for the file. If you cannot find the file you need, ensure that it has been uploaded to a library in Salesforce CRM Content or Salesforce Files.

Select which users can access this file: all users, internal users, or shared users.

Select the campaign to add the lead. If you cannot find the campaign you need, try refreshing the results.

Select an existing lead to add to the campaign. If you cannot find the lead you need, try refreshing the results.

Relative path to your Apex REST endpoint. Include namespace if required. Examples: myEndpoint, myNamespace/myEndpoint, myNamespace/v1/doThing.

JSON object for URL query parameters. Use format: {"debug": true, "limit": 10}. Avoid secrets in query parameters for security.

JSON object for additional HTTP headers. Use format: {"Sforce-Call-Options": "client=Zapier"}.

Raw request body sent to your Apex REST endpoint. Enter exactly what your Apex method expects: JSON objects, arrays, strings, numbers, etc. No transformation applied.

Request timeout in milliseconds. Defaults to 30,000 (30 seconds).

Select an existing lead to convert. If you cannot find the lead you need, try refreshing the results.

Select an existing opportunity for the lead. Salesforce creates a new opportunity by default when the lead is converted.

Select "Yes" to create a new opportunity when the "Opportunity" field is empty. Select "No" or use the "Opportunity" field if you don't want to create a new opportunity.

Select the lead's status after being converted to a contact in Salesforce.

Enter a file object or URL. [Learn about files](https://help.zapier.com/hc/en-us/articles/8496288813453-Send-files-in-Zaps).

Pick the type of object you want to attach the file to (Note: we do our best to support all objects, but due to their complex nature, some may not work flawlessly).

Select "Yes" to use active Salesforce assignment rules. Select "No" if you don't want to use assignment rules when creating this record.

Select the type of record to attach this note to (optional).

Enter a file object or URL. [Learn about files](https://platform.zapier.com/docs/files)

Select an object to use to attach the file.

Select 'Yes' to use active Salesforce assignment rules. Select 'No' if you don't want to use assignment rules when creating this lead.

Depending on your Salesforce configuration, deleted records may be moved to the Recycle Bin where they can potentially be restored for up to 15 days. However, if the Recycle Bin is disabled manually emptied, or after the retention period expires, deleted records and their associated data cannot be recovered. [Learn More](https://help.salesforce.com/s/articleView?id=xcloud.home_delete.htm&type=5)

Select an object type for the record to delete.

Optional: Enter additional key-value pairs for flow input variables. This field can be used as an alternative to the dynamic fields above, or to provide additional parameters not detected automatically.

Select the Salesforce report to execute. This will show your recently viewed reports.

Include detailed row-level data in addition to summary data. When false, returns only summary information.

Select how many custom filters you want to add (0-5). Leave blank for no custom filters.

Field API names for row groupings. Example: Account.Name, Opportunity.StageName.

Field API names for column groupings. Example: FISCAL_QUARTER(CloseDate).

Aggregate identities for summary calculations. Use format like "s!Amount" (sum), "a!Amount" (average), "m!Amount" (minimum), "x!Amount" (maximum).

Field API names to include in detailed data. Only used when "Include details" is true.

Fields to sort by with direction. Format each as "FIELD_NAME:asc" or "FIELD_NAME:desc".

Format of the report output. Defaults to the report's original format if not specified.

Advanced report metadata options as key-value pairs. Common options: currency (USD/EUR/GBP), division (data segmentation), showGrandTotal (true/false), reportBooleanFilter (filter logic).

Email addresses to send to (comma-separated). Maximum 150 total recipients including CC and BCC.

CC email addresses (comma-separated). Maximum 150 total recipients including To and BCC.

BCC email addresses (comma-separated). Maximum 150 total recipients including To and CC.

Select the contact to update. Use a [custom value](https://help.zapier.com/hc/en-us/articles/8496241696141-Add-custom-values-to-dropdown-menu-fields-in-Zaps) to select a contact from a previous step.

Select the lead to update. Use a [custom value](https://help.zapier.com/hc/en-us/articles/8496241696141-Add-custom-values-to-dropdown-menu-fields-in-Zaps) to select a lead from a previous step.

Select the record to update. Use a [custom value](https://help.zapier.com/hc/en-us/articles/8496241696141-Add-custom-values-to-dropdown-menu-fields-in-Zaps) to select a record from a previous step.

Select "Yes" to use active Salesforce assignment rules. Select "No" if you do not want to use assignment rules when creating this lead.

Select “Yes” to [stop this Zap step](https://help.zapier.com/hc/en-us/articles/20505304170637-Review-Zap-run-statuses#h_01HD20969HPZ01ENM30NQR79X5) if the app returns an error and enable automatic authentication refresh. Select “No” to run the Zap step regardless of errors. Learn more about [API Request action error handling](https://help.zapier.com/hc/en-us/articles/12899473501453#h_01JKRBY68EDXBB1V817DSTRZ0N).

Requests can only be made to domains associated by this application. Read more about [API Request Setup](https://help.zapier.com/hc/en-us/articles/12899607716493).

Any parameters added to a URL will be URL-encoded and appended to the request URL to pass additional data to the API request.

These headers and values will be applied to the request in addition to any headers created as part of authentication. Authentication headers are added automatically.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, `{"foo": "bar"}` is perfectly valid.

Salesforce is a leading enterprise customer relationship manager (CRM) application.

Salesforce

Instantly build dynamic interfaces that connect to Zaps and a data source (like Tables). Interfaces gives you a drag-and-drop way to build visual workflows for any business process, without writing code.

Zapier Interfaces

Find if an existing record exists in Salesforce from a new scanned badge or business card in Handshook. Create one if it doesn’t exist and use assignment rules in Salesforce to assign the contact. This Zap saves your team hours by eliminating the need for tedious manual entry of leads and SQLs into your CRM.

Handshook + Salesforce

Find Salesforce records from new scanned badges or business cards in Handshook

Supported triggers and actions

New Connection

About Handshook

Related categories

About Salesforce

Related categories

Similar apps

Zapier Interfaces

Related Zap Templates

Related Zap Templates