Bigin trigger by Updated Event?

Hi Troy

That worked.  Event updates now trigger our Zap. Thanks!

However, now we’re stuck on the next step.  We have retrieved a Contact ID from the Event “Related To” field and wish to access other fields from the contact.  We have tried both the Search Contact step and the Update Contact step.  The Search Contact step does not have a Contact ID Option.  The Update Contact step works the wrong way round, modifying the Bigin record rather than getting information!

So how to access details of a Contact record based on its Contact ID?

Now getting a 401 “invalid oauth token” error.  This suggests that we need to pass a different access token as an authorization header.  However, the notes in the Zap step say “Authentication headers are included automatically”.  Also, if we do get or generate new tokens, it’s not obvious where to put them!

Here

That changed the response, so it definitely helped.  However, we still have an error -- now “invalid oauth scope to access this URL”

So I assume from this that I need to generate a new authentication token, with the relevant scope.  The Bigin API console offers five different types of “client type”.  I assume that Zapier is a “server based app”.  In that case, please help me complete the “Client name”, “Homepage URL” and “Authorised Redirect URIs” fields.

I appreciate that I’ll need to make a new connection once that’s done, but when I get the token, where do I enter it in Zapier?

Sorry, but I have no idea how or where to “adjust scope settings/permissions in Bigin for the Bigin account that is/will be re/connected to Zapier”!

@NoahFr 

When connecting Bigin to Zapier these are the set scopes:

So these do not include reading or updating records in the “contacts” and “pipelines” and “activities” modules.  Ideally, at this point, the scope should include {ZohoBigin.modules.ALL}

Where is the scope set?  How can we change it?

We are already using a webhook as the trigger for this Zap, but I am not at all clear how to mix Webhooks and API calls to deal with a sequence including an authentication handshake (along with keepalive?) and then accessing the data that we actually need!