Aditi S.

Just a quick follow up on this: Admin consent only approves permissions - the actual mailbox owner still needs to sign in once. Please go back to Clay, then reconnect and complete the Microsoft login as the inbox user (not just as an admin).

Hi Alexis - thanks so much for reaching out. From what I can see, it seems like you're completing Microsoft’s admin consent flow. Admin consent only approves the Clay app for the tenant - it does not connect an email account and does not return OAuth code / state values, which is why Clay shows that message. ​

What to do next:

Let us know if it still doesn’t work after trying the “Add email accounts” flow.

Hi Lidiia - thanks so much for reaching out and for your patience here.

I believe this should be restored now and you should be able to share a workbook as a template again:

Sounds good Miguel! Will close this out for now but feel free to reach out in a new conversation if you have more questions

Are there any other questions I can help you with?

Hi Ayush - thanks so much for reaching out and for your patience here. Could you please reach out to us via your work email at support@clay.com? We would then be able to support your request for this there.

We don't support that unfortunately - all Claygent models require access to the internet to be able to run.

Of course - happy to help!

I am not too sure what you mean about the Claygent model part of things - do you mind expanding a bit more?

Hi Miguel - thanks so much for reaching out.

The reason you may not see some LinkedIn profiles come through is because if a profile has limited public visibility, you're unable to retrieve the full profile content.

I'd recommend using our Enrich Person action for live data on people's profiles.

Hope that helps!

Hi Yannick - thanks so much for reaching out and for your patience here. I would love to get some more context on what you mean by sending rows in order to "Enrich" the data in your other table. It sounds like what you're wanting to do is send additional information that has been added into Table A to be pushed to Table B. The lookup single row feature could be helpful here, as it's not just for flagging or filtering duplicates. If there is a common field between Table A & Table B (i.e. a domain) - you can use this as a Lookup identifier and perform the lookup on that field. What will happen then is that within the Lookup Row column you'll be able to see the rows pulled in from the other table as follows and then you can add in those columns:

If you're happy to share a link to the table in which you're working through this, I can do a test setup of this to help demonstrate how this can be done.