Hi ​@Stan_w_Gifford,

Welcome to the Community.

If you're facing issues retrieving contact details in Dynamics 365 using GUIDs through Zapier, first check if Zapier's Dynamics 365 integration supports searching by GUID. If not, consider using "Webhooks by Zapier" to make a custom API call and retrieve contact details directly. Ensure your Dynamics 365 app is up to date, and if needed, reach out to Zapier support to see if future updates might include this functionality. These steps should help you find a workaround effectively.

Feel free to ask if you have further questions or need additional support.

I had a brief (shudder) look at webhooks.

I have (almost) solved the issue.

Basically I had already been sending opportunity data to SQL Server (via Power automate) so added a status field to the SQL server table and did a trigger of that - actually what I did was trigger on that status field being changed, then a sql query to get top 1 of my data (from a view with a where clause). This would either return the first record, process it (create lead) and update the trigger field. That should fire the ZAP again and it will either process the next record - or the SQL query will return no rows - in which case the zap will shut itself down.

Hey there, ​@Stan_w_Gifford 

Great to hear you’ve almost solved it—nice work!  

I’m not sure Webooks app would work for finding the contact as it’s not able to handle OAuth for the request, which is what the Microsoft Dynamics API would require. The API Request (Microsoft Dynamics 365 CRM) action would be a better option as it would automatically handle the authentication side of the request to the Microsoft Dynamics 365 CRM API.

Similar to a Webhooks action you’d need to reference Microsoft’s API documentation to set up the request so it’s a bit more advanced, but I’d be happy to lend a hand if you run into any errors or get stuck at all. And I’d recommend checking out our Create an API Request action guide to learn more about how to work with those sorts of actions.

Keep us posted on how you get on, want to make sure you’re all set! 

Thanks for the offer.

Currently my ZAP is ‘almost’ working - when I say almost it is not re-triggering itself.

Essentially there could be many records in my SQL database that need to be pushed to Buz.

I trigger on any update to the database (via a last updated field - Datetime

Once I have been triggered, I select top 1 * from my view that shows records to be sent to Buz. If none found, Zap should finish.

Otherwise I create the lead in Buz (This bit working perfectly) then issue a SQL Update to update the lastupdated field of the sql record with getdate(), and set a couple of bit fields used in the view to not select this record again.

I anticipated that the ZAP would finish itself, and would be triggered by the update to lastupdated date from the previous zap run - but it does not get triggered again :-(

Scratch previous reply.

It is now re-triggering properly (must have been a glitch in the matrix)

Thanks for assist

Stan

Wow! Thank you for sharing your resolution got the Zap running. This will significantly help our Community members to have as a reference for the same issue.

I think it is a case of using the best tools for the job.

power automate (flow) can handle data verse data easily. It is also good at being triggered from updates to a table. It is pretty cool with sql server.

azure database can be a very low cost way of creating a secure repository as an intermediate medium.

zaps appear to be very easy to implement and can be fired from sql server updates. - my zap has three steps!

so with judicious design you can get around the following limitations;

1. power automate cannot interface to Buz without having to go thru pain (api requests etc - learning effort)

     2. Zaps are not able to query dynamics via entity primary key (guid)

stan

Thanks so much for the update, ​@Stan_w_Gifford—so glad to hear your Zap is triggering again now! 

And couldn’t agree more with you on using the best tools for the job! It’s all about finding the right fit for your workflow.

Seems like you’re all set for now, but do reach back out if you need help with anything else. In the meantime, happy Zapping!