Vk new actions sources

[jcortes]

Scopes currently added

Acording to permissions these are the current scopes added in the app

• 4 -> photos
• 16 -> video
• 1024 -> status
• 4096 -> messages
• 8192 -> wall
• 262144 -> groups

Even though we are still getting Access denied error request messages

Update

Now the only scope is

• 134217728 -> market

But still getting same Access denied errors

Actions

• Get Wall Posts | Returns a list of posts on a user wall or community wall. See the docs here
• Get Wall Post | Returns a post from user or community walls by ID. See the docs here
• Get Photos | Returns a list of a user's or community's photos. See the docs here
• Get Videos | Returns detailed information about videos. See the docs here
• Getting access denied error Access denied: no access to call this method
• Get Authenticated User | Returns the current account info. See the docs here
• Getting access denied error Access denied: no access to call this method
• Create A Community | Creates a new community. See the docs here
• Getting access denied error Access denied: no access to call this method

Sources

• New Wall Post | Emit new event when a wall post is created. See the docs here
• Gets Access denied: no access to call this method when trying to create the webhook so the source doesn't get deployed
• New Photo | Emit new event when a photo is created. See the docs here
• Gets Access denied: no access to call this method when trying to create the webhook so the source doesn't get deployed
• New Video | Emit new event when a video is created. See the docs here
• Gets Access denied: no access to call this method when trying to create the webhook so the source doesn't get deployed

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
pipedream-docs	✅ Ready (Inspect)	Visit Preview	Oct 12, 2022 at 7:42PM (UTC)
pipedream-docs-redirect-do-not-edit	✅ Ready (Inspect)	Visit Preview	Oct 12, 2022 at 7:42PM (UTC)

[dylburger]

Thanks for submitting this PR! When we review PRs, we follow the Pipedream component guidelines. If you're not familiar, here's a quick checklist:

• Create components to address specific use cases whenever possible
• Component keys should follow the format app_name_slug-slugified-component-name
• Components should follow the standard directory structure
• Prefer Node.js client libraries to REST APIs
• When making API requests, handle pagination to ensure all data / events are processed
• Use secret props to capture sensitive data
• Props and methods should be defined in app files whenever possible
• Document methods with JS Docs
• Use optional props whenever possible, and set a default value where you can
• Use async options to accept user input wherever possible
• Create subscription webhooks sources (vs polling sources) whenever possible
• Always emit a summary with events
• Use a built-in deduping strategy wherever possible
• When building webhook sources, follow these best practices
• When building polling sources, follow these best practices

[jcortes]

Hi @SGZabrav can you please give me a hand on trying to understand why am I still getting Access denied when calling these endpoints. Thanks in advance!

[SGZabrav]

Hi @SGZabrav can you please give me a hand on trying to understand why am I still getting Access denied when calling these endpoints. Thanks in advance!

I can only use ready-made pipedrim scripts. Can you tell me the specific steps to check? Also, VK has a representation on github, but I don’t know to whom specifically to write for clarification.

P.S. I see some diference between English and Russian localisations. There is:

video
(+16)
(1 << 4)

Maybe this can help...

[jcortes]

Hi @SGZabrav can you please give me a hand on trying to understand why am I still getting Access denied when calling these endpoints. Thanks in advance!

I can only use ready-made pipedrim scripts. Can you tell me the specific steps to check? Also, VK has a representation on github, but I don’t know to whom specifically to write for clarification.

P.S. I see some diference between English and Russian localisations. There is:

video
(+16)
(1 << 4)

Maybe this can help...

Hi @dannyroosevelt can you give me a hand with this one please?

[dannyroosevelt]

Hi @SGZabrav can you please give me a hand on trying to understand why am I still getting Access denied when calling these endpoints. Thanks in advance!

I can only use ready-made pipedrim scripts. Can you tell me the specific steps to check? Also, VK has a representation on github, but I don’t know to whom specifically to write for clarification.
P.S. I see some diference between English and Russian localisations. There is:

video
(+16)
(1 << 4)

Maybe this can help...

Hi @dannyroosevelt can you give me a hand with this one please?

I'm not following. @SGZabrav are you able to check out this branch are try testing these actions in your account? We are not able to get the actions working and think it might be a permissions or scope related issue.

You'll need to,

1. Check out this branch gh pr checkout 4451
2. Install the Pipedream CLI and log into your Pipedream account
3. Then pd publish the actions to test

[SGZabrav]

Hi @SGZabrav can you please give me a hand on trying to understand why am I still getting Access denied when calling these endpoints. Thanks in advance!

I can only use ready-made pipedrim scripts. Can you tell me the specific steps to check? Also, VK has a representation on github, but I don’t know to whom specifically to write for clarification.
P.S. I see some diference between English and Russian localisations. There is:

video
(+16)
(1 << 4)

Maybe this can help...

Hi @dannyroosevelt can you give me a hand with this one please?

I'm not following. @SGZabrav are you able to check out this branch are try testing these actions in your account? We are not able to get the actions working and think it might be a permissions or scope related issue.

You'll need to,

1. Check out this branch gh pr checkout 4451
2. Install the Pipedream CLI and log into your Pipedream account
3. Then pd publish the actions to test

Can this really be done by a non-developer/non-programmer (me)?
What I have now:
1/

gh pr checkout 4451
? Which should be the base repository (used for e.g. querying issues) for this directory? PipedreamHQ/pipedream
Switched to a new branch 'vk-new-actions-sources'
branch 'vk-new-actions-sources' set up to track 'github-desktop-jcortes/vk-new-actions-sources'

2/ Done
3/ From now on, I ask for more details. All I get at this step are errors.

[dannyroosevelt]

Hi @SGZabrav can you please give me a hand on trying to understand why am I still getting Access denied when calling these endpoints. Thanks in advance!

I can only use ready-made pipedrim scripts. Can you tell me the specific steps to check? Also, VK has a representation on github, but I don’t know to whom specifically to write for clarification.
P.S. I see some diference between English and Russian localisations. There is:

video
(+16)
(1 << 4)

Maybe this can help...

Hi @dannyroosevelt can you give me a hand with this one please?

I'm not following. @SGZabrav are you able to check out this branch are try testing these actions in your account? We are not able to get the actions working and think it might be a permissions or scope related issue.
You'll need to,

1. Check out this branch gh pr checkout 4451
2. Install the Pipedream CLI and log into your Pipedream account
3. Then pd publish the actions to test

Can this really be done by a non-developer/non-programmer (me)? What I have now: 1/

gh pr checkout 4451
? Which should be the base repository (used for e.g. querying issues) for this directory? PipedreamHQ/pipedream
Switched to a new branch 'vk-new-actions-sources'
branch 'vk-new-actions-sources' set up to track 'github-desktop-jcortes/vk-new-actions-sources'

2/ Done 3/ From now on, I ask for more details. All I get at this step are errors.

Ah got it, yes -- do you have any developers you are working with who might be able to assist? By the way, are you working with VK? Are you able to put us in touch with anyone there?

[SGZabrav]

I contacted VK support.
I was asked exactly how we get the token.
I sent information from https://pipedream.com/apps/vk and specifically the Authentication section.
Got the answer: (google translate)

"The fact is that the key can only be obtained with an application on the platform, which is created here: https://vk.com/apps?act=manage. It is the application ID that should be in place of the client_id.
Unfortunately, from the information provided, we can't be sure that Pipedream is using it, and not the profile ID, for example."

[dannyroosevelt]

I contacted VK support. I was asked exactly how we get the token. I sent information from https://pipedream.com/apps/vk and specifically the Authentication section. Got the answer: (google translate)

"The fact is that the key can only be obtained with an application on the platform, which is created here: https://vk.com/apps?act=manage. It is the application ID that should be in place of the client_id.
Unfortunately, from the information provided, we can't be sure that Pipedream is using it, and not the profile ID, for example."

Are you able to either connect us with VK support directly, or loop them into this ticket? Getting the access token does not appear to be the core issue (some endpoints work) -- the issue is when actually making requests to specific endpoints, like video.get for example. So maybe we are requesting scopes incorrectly?

[SGZabrav]

Are you able to either connect us with VK support directly, or loop them into this ticket? Getting the access token does not appear to be the core issue (some endpoints work) -- the issue is when actually making requests to specific endpoints, like video.get for example. So maybe we are requesting scopes incorrectly?

@dannyroosevelt

No, unfortunately, I will not be able to connect to the ticket on GitHub, but they can contact us on their own, for example, to our mail support@vk.com.

As for the messages section, I can say for sure that access to it must be requested through VKontakte Support. We have restricted its use to third party developers for the sake of security.

As for other sections*, I see a pattern there in the need to obtain exactly the access key of the platform user. You can read about how to get it here: https://dev.vk.com/api/access-token/getting-started#К.. or here in English https://vk.com/dev/access_token?f=1 . user token.

*https://dev.vk.com/method/video.get
https://dev.vk.com/method/photos.get
https://dev.vk.com/method/wall.get
https://dev.vk.com/method/groups.get