When building integrations there is always a risk of something unexpected to happen, here are some of these risks and how you can mitigate them.

Malformatted Data

When sending data to an external REST end-point it is crucial that that system understands that data.

Some systems are more or less forgiven when it comes to expected values. 

Examples:

• Sending a String but external system expects an integer

Mitigation

Always create a Catch Action that sends fewer fields over with a comment that there is more data in JIRA.

Miss match of data entries

This usually happens when it comes to sending values that will be treated as a select list, radio button, or other multi-choice fields

The problem

JIRA sends a value, lets say "Sweden" that should set a field on Freshdesk called countries, which is of type dropdown.

If "Sweden" does not exist in that drop-down, then Freshdesk will respond with a 400 and the call will fail.

Mitigation

Always create a Catch Action that sends Default value for the fields that are sensitive to values.

Catch Action will trigger on any error code and perform a second Request Action and acts as a fallback to not miss things.

Attachment Size limit

Some external systems have a limit on the maximum attachment size, if that is exceeded the system might reject the call returning a 400 or 500.

Mitigation

Always create a Catch Action that sends the call without the attachment, but with a comment that there are Oversized attachments in JIRA.