Input 

Document

• Min:0

• Max:1

• HubSpot Read

• Mapper

• Copy

A document containing key/identifier of the data object to delete.

Output

Document

• Min:0

• Max:1

• Mapper

• Copy

• Email Sender

A document containing the entity ID and the status of the delete operation.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the pipeline by choosing one of the following options from the When errors occur list under the Views tab:

• Stop Pipeline Execution: Stops the current Pipeline execution if the Snap encounters an error.

• Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

• Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Label*

Default Value: HubSpot Delete
Example: N/A

String

Specify a name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.

Entity*

Default Value: Association
Example: Company

String

Select the data object to delete.

Action*

Default Value: N/A
Example: Delete a company

String

Select the delete-action to perform on the entity selected above. Click the Suggestion icon to see the list of supported actions. 

Required Parameters

Use this field set to enable the Snap to perform a specific action.

Parameter

Default Value: N/A
Example: company_id

String

Specify the names of the required parameters. Click the Suggestion icon to see the list of supported parameters.

Value

Default Value: N/A
Example: 123561234

Multiple

Specify the values of the required parameters. The data type of this field depends on what parameter name you selected or entered which can be String, Integer, Boolean, etc.

Connection timeout*

Default Value: 30
Example: 30

Integer

Specify the time in seconds for the Snap to wait before terminating the request because of a failure to establish a connection to the target service.

Number of retries*

Default Value: 0
Example: 0

Integer

Specify the maximum number of retry attempts to make if a connection failure or timeout occurs.

Retry interval (seconds)*

Default Value: 0
Example: 0

Integer

Specify the number of seconds for which the Snap must wait before attempting recovery from a network failure.

Retry policy

Default Value: Connection errors
Example: Connection and API limit exceeded errors (429)

Dropdown list

Choose the retry policy for connection and error responses. The available options are:

• Connection errors: Select this option when the client fails to establish a secure connection to the server.

• Connection and API limit exceeded errors (429): Select this option when the 10-second or daily limit is exceeded.

Snap Execution

Default Value: Execute only
Example: Validate & Execute

Dropdown list

Indicates how the Snap must be executed. Available options are:

• Validate & Execute: Performs limited execution of the Snap (up to 50 records) during Pipeline validation; performs full execution of the Snap (unlimited records) during Pipeline execution.

• Execute only: Performs full execution of the Snap during Pipeline execution; does not execute the Snap during Pipeline validation.

• Disabled: Disables the Snap and, by extension, its downstream Snaps.

Missing required parameters.

There is a required parameter that was not provided.

Verify whether all required parameters are configured.

You have reached your ten secondly rolling limit.

There are too many requests to REST endpoint.

Select Connection and API limit exceeded (429) errors in the Retry Policy and adjust the values for “Number of retries” and “Retry interval”.

You have reached your daily limit.

There are too many requests to REST endpoint.

The maximum number of daily requests has been reached, and no further requests can be made until it resets. For more information refer to API Meters.