Problem with Process Builder Invocable Method and Webservice Call out

Question

I am trying to execute a web service call to our backend system when the opportunity is closed/won. I am attempting to do a POST to our endpoint. All the api call is really carrying the account name and a few structural detail back (All listed below). My problem is that when the trigger executes I get the following error in the debug logs "System.CalloutException: You have uncommitted work pending. Please commit or rollback before calling out".

The Process Builder Passing in the company name:

APEX Class

public class Play2 {
@TestVisible static HttpResponse res;

@InvocableMethod
public static void sendNotification(List<String> name) {



    HttpRequest req = new HttpRequest();
    Http http = new Http();
    String payload = JSON.serialize(
        new Map<String, String> {
            'companyName' => name.get(0),
            'salesforceAccountType' => 'Company',
            'salesforceSynchStatus' => 'Enabled'
        }
    );

    req.setEndpoint('https://TheEndPoint');
    req.setMethod('POST');
    req.setHeader('Authorization', 'The Mighty API KEY');
    req.setHeader('Content-Type', 'application/json');

    req.setBody( payload );
    req.setCompressed(true); 

    try {
        System.debug('Point 1');
        res = http.send(req);
        System.debug('Point 2');
    } catch(System.CalloutException e) {
        System.debug('Callout error: '+ e);
        System.debug(res.toString());
    }
}
}

Answer 1

Apex can be annoying like that: limitations in termos of callouts and DML. What we've done to work around that is to make callout in the future method. Your invocable would call the future and pass the map. The future would construct the request and send it out. Your future should be annotated with @future(callout=true) to be able to make callouts.

Answer 2

@InvocableMethod makes the method visible to process builder.

@future(callout=true) makes the process builder able to use methods that callout since there can only be asyncronous callouts allowed from an invocable method.

public static void calloutmethod(List name){} - the @future callout needs to be in a separate method that is called by the @invocableMethod sendNotification(List name) since you cannot callout directly from a method annotated with the @invocableMethod.

-- @TestVisible static HttpResponse res; is probably his unique way of replying with a mock callback and uses this in his test classes. You should at least implement HttpCalloutMock in your tests against this the Play2 class.

Answer 3

Try this

public class Play2 {
@TestVisible static HttpResponse res;

@InvocableMethod

public static void sendNotification(List<String> name) {


calloutmethod(name);

}

@future(callout=true)

public static void calloutmethod(List<String> name){
  // Your callout logic
}

}