The IP addresses here in the "Accepting requests from the Boomi Enterprise Platform" section can be trusted if you use any connector that has the following features/actions:

• OAuth 2.0 token generation (Authorization Code and Resource Owner Credentials)
• Browsing and importing objects for connector operations using the "Use public runtime cloud" or "Cloud" option
• Testing connections using the "Use public runtime cloud" option

If you are using any one of those features, you will see requests from the platform and might need to create trusted platform IP addresses depending on your security. Otherwise, you do not need to create trusted platform IP addresses. 
 

Do I need to create trusted platform IPs when using this connector?

Here is the general decision tree,

1. Does the connector use OAuth 2.0, Authorization Code or Resource Owner Credentials? If yes, you need to created trusted platform IP addresses. Connectors using Client credentials or JWT Bearer Tokens will not see requests from the platform
2. Are you planning to import operations using the public runtime cloud option instead of your own local runtime? If yes, you need to trust the platform IP addresses
3. Are you planning to test the connection (if applicable) using the public runtime cloud option instead of your own local runtime? If yes, you need create trusted platform IP addresses
4. In all other cases (except ones listed below), you do not need to create trusted platform IP addresses

As new connectors come out, they should generally follow the pattern above. Connectors evaluated were added as of May 2020. 
 

List of connectors that will definitely see requests from the platform

The endpoints in these connectors will see requests from the platform because token requests are sent and managed by the platform and there are no other options.

• Google Ad Manager
• Google G Suite
• Google Sheets
• Slack

 

List of connectors that might see requests from the platform

The endpoints will see requests from the platform if you choose one of the features (like OAuth 2.0, Authorization Code or Resource Owner Credentials), but if you use the other options (like Client Credentials or JWT Bearer Token), you do not need to created trusted platform IP addresses.

• Google BigQuery
• Google Pub Sub
• Google Storage
• HTTP Client
• HTTP PATCH Client
• Microsoft Dynamics 365 for Customer Engagement
• Microsoft Dynamics 365 for Finance and Operations
• OData Client

 

List of connectors that will see requests from the platform only on the import

When importing in the operation there is not an option to choose another runtime so the initial import uses the platform. 

• Aprimo
• Lumesse TalentLink - Partner Connector
• NetSuite OpenAir
• Salesforce
• ServiceNow
• Taleo
• Workday

 

All other connectors

All other connectors will not see any requests from the platform or you can choose to test the connection or import in the operation using the platform but you do have the option to choose other runtimes. You do not need to create trusted platform IP addresses in these cases. The endpoints will see the request from the server the runtime is installed on. If you plan to execute your process on other runtimes, there is no real advantage to trusting the platform IP addresses just to test the connection or import an operation (since you can test/import with the runtime you plan to execute with). 

Note: for some connectors like Quickbooks you'll see a cloud option during the operation import but it's not really asking the platform to browse/import objects. There's already a predefined list of objects that can be imported and will allow you to choose from the list of objects whether a connection was defined or not. Some connectors lets you generate an operation without using any connection information (or correct connection information) since they have a predetermined list already.