how to call Send an HTTP request to SharePoint for a REST endpoint not exposed by the standard connector

By Sai Kiran Pandrala · Last verified: 2026-05-31 · Source: in-product help, community forums (r/nocode, r/automation, r/GoogleAppsScript, r/PowerAutomate, r/n8n, r/make, r/ClaudeAI), vendor status pages and changelogs, vendor help centers

Running into how to call Send an HTTP request to SharePoint for a REST endpoint not exposed by the standard connector on Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 is one of the more common stalls I see when I am deep in a scenario or a script and the platform suddenly refuses to cooperate. My standard pattern for this is to capture the run history first, then walk the fix below - here is what actually moves the needle when the vendor docs are too generic and you do not have time to file a support ticket.

What how to call send an http request to sharepoint for a rest endpoint not exposed by the standard connector actually involves on Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026

On Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 on a fresh callout the tools I crack open first are Power Platform Center of Excellence Starter Kit Flow inventory, PnP PowerShell `Get-PnPListItem -PageSize` for parity with connector behavior, Graph Explorer (developer.microsoft.com/graph/graph-explorer) for cross-checking item queries. Each of these surfaces a different layer of the failure - keep at least the first one in your personal notes so the next time this happens you do not start cold.

For verification on Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026, the methods that survive contact with a real Monday-morning workload are use the OData test `?$filter=AuthorId eq 14` directly in browser at site/_api/web/lists/getbytitle()/items and in run history confirm outputs Body.value array length matches expected count. Anything less than that and you are shipping on vibes.

Authoritative sources for Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 that I cross-reference before committing to a fix: learn.microsoft.com/en-us/sharepoint/dev/business-apps/power-automate/guidance/working-with-get-items-and-get-files, learn.microsoft.com/en-us/connectors/sharepointonline, learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/working-with-folders-and-files-with-rest. Marketing blog posts and Medium writeups are signal, not ground truth.

The rest of this page is the structured fix path. Start with diagnose, then remediation, then the automation options so you do not have to do this by hand the next time it surfaces. Verify and safety sections at the end are the discipline that keeps the fix from regressing the next time you open the platform.

Spot the symptom

Second pass: open the Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 workspace admin or settings panel and look at the audit log or activity feed for the failing window. Most modern automation platforms surface an audit trail (the platform's execution history, the connector run log, the integration activity feed). The audit log tells you whether the failure was your action, a teammate changing a connected account in the same minute, or a platform-side rollout. Many "permission denied" or "connection not found" reports trace to a credential-level change pushed in the same admin panel in the previous hour - the audit trail makes that obvious without guesswork.

Eighth: diff the Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 setup against its last known good state. Ask the obvious question - what changed in the 72 hours before the failure started? Did the platform auto-update overnight (check the About panel for the engine version vs the previous version you wrote down in your notes)? Did you install a new browser extension, a new menu-bar utility, or a new VPN that intercepts the connection? Did you switch accounts, accept a new workspace invite, or change your default workspace? Did your team admin push a new connector policy, enable SSO, or add an SCIM provisioning rule? Use the in-product audit trail or notification feed to anchor "before vs after" so you are not guessing. Cross-check the vendor changelog and community forum for the exact build - if a regression hit a batch of users in the same week, the community catches it before the official changelog admits it. Record the suspect ranking, then disprove suspects one at a time with the cheapest test first (browser private window before extension uninstall, second account before account-wide reset).

Fifth: replay the failing run against a second account or a second connector on the same Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 workspace. The point is to isolate "my credentials" from "my account" from "the whole workspace." If a teammate's identical scenario works but yours does not, the failure is local cache or a stale OAuth grant. If the same scenario fails for everyone in the same workspace, you have a tenant-wide config change or a vendor-side incident. Pin the platform version explicitly while you do this: the platform's About panel, the build hash in the footer, or the engine version returned by a diagnostic call. The version pin is what isolates "their rollout broke me" from "my client is out of date."

Field notes from real Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 incidents

Last sprint I lost most of an afternoon to an Power Automate SharePoint Connector bug before remembering that Power Platform Center of Excellence Starter Kit Flow inventory would have surfaced the failing step in under a minute. The fastest sanity check I know for an Power Automate SharePoint Connector change is `set Top Count to 5000 and Pagination = On (5000) in the action Settings panel`; if that returns the expected value, I ship the flow and move on.

After any change to an Power Automate SharePoint Connector automation I run `open the list Settings > Advanced settings and confirm the list view threshold = 5000` to confirm the run actually held, two seconds, one call, zero ambiguity. For Microsoft workflows I keep a personal log of "what bit me in Power Automate SharePoint Connector and how I unstuck it", writing it down the first time saves the next afternoon.

Tools I actually reach for

For most Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 stalls I start with SharePoint admin center Site usage page for throttling signals, fall back to Postman with a SharePoint app-only token for endpoint validation, SharePoint REST API tester at /_api/web/lists in the browser, Power Platform Center of Excellence Starter Kit Flow inventory when SharePoint admin center Site usage page for throttling signals cannot surface the answer, and keep Power Automate run history Inputs and Outputs of the Get items action handy for the cases where neither answers. That ordering is not academic - it matches the layers of the failure as they tend to surface, so the cheapest signal lands first and the heavier tooling only comes out when the simpler answer does not hold up. My muscle-memory shortcut for this is to run the first tool while the failing screen is still open, not after I have already restarted the platform.

Verification I run before I call it fixed

Before I mark a Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 stall resolved, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheaper checks gate the more expensive ones.

use the OData test `?$filter=AuthorId eq 14` directly in browser at site/_api/web/lists/getbytitle()/items

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

open the list Settings > Advanced settings and confirm the list view threshold = 5000

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

set Top Count to 5000 and Pagination = On (5000) in the action Settings panel

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

run `Get-PnPListItem -List 'Tasks' -Fields ID,Title -PageSize 2000` for parity check

Only when every line above runs clean do I close the loop and update my notes with the timestamps.

Where I check first when the docs disagree

When two sources contradict each other on a Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 detail, the disambiguation order I lean on is stable. I usually check learn.microsoft.com/en-us/sharepoint/manage-lists-and-libraries-with-many-items for the ground-truth view on this part of Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026. I usually check learn.microsoft.com/en-us/power-automate/guidance/coding-guidelines/understand-limits for the ground-truth view on this part of Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026. I usually check learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/working-with-folders-and-files-with-rest for the ground-truth view on this part of Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026. I usually check learn.microsoft.com/en-us/connectors/sharepointonline for the ground-truth view on this part of Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026. Marketing blog posts and Medium writeups are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim.

Solution-focused remediation path

Before any destructive step on a Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 workspace, slow down and stage rollback. Snapshot the current platform version, the current workspace settings (Settings -> screenshot every tab), the connected-apps list, the current sharing policy, and the current member list to a notes entry first. Capture the failing screenshot, the Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 incident id if any, and the timestamp window. Photograph (screenshot) the workspace state from two angles: the scenario or script that is failing, and the workspace settings page that controls the relevant policy. Then do the destructive step (revoke a connector, change a sharing default, remove a member, delete a connected app) inside a test workspace or a test scenario first, never the whole workspace. Capture the platform version, the API permissions, the connected-app list, the workspace member roster, and the relevant integration log snapshot to your notes before the destructive step. Decision point: if you are on a paid plan, the cheapest correct path is almost always to open the in-product support chat in parallel with the rollback - the support rep can confirm whether a vendor-side rollout is responsible while you are still staging the change, which avoids a needless workspace edit if the fix is server-side.

When the Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 fault tracks to integration failures, automation delays, or webhook drops from the trigger source (the trigger source, the connector, the upstream provider), treat the integration plane as suspect. Open the integration log in the connected service (the trigger source's webhook log, the platform's connector run history) and read the response status the Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 endpoint actually returned - most "scenario not firing" reports are actually "webhook firing but the connector failed and the platform backed off." Verify the connected account is still authorized (the OAuth grant in Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 is not silently revoked) and that the trigger event is what you think it is. Decision point: if the trigger is firing but Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 is rate-limiting it, throttle the scenario (bump the polling interval, add a sleep module, enable batch mode) and re-run. Verify the connected workspace is the right workspace - a common foot-gun is the personal workspace being authorized while the work workspace holds the data.

For Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 integrations where rate limits or plan quotas are suspect, read the in-product hints honestly. "You have reached the limit for this workspace" usually means you hit an operation, task, or run cap on the current plan tier. "Slow down, you are sending requests too quickly" is the rate-limit signal on the trigger source or destination API. "This payload is too large" is the per-call cap. Each is telling you the exact same thing in a Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026-specific dialect. Apply exponential backoff for API-driven runs (base 1s, double up to 60s, retry up to 5 times) and split a large batch into chunks of 100 records at a time. Decision point: if you are hitting the quota sustained rather than in bursts, upgrade the plan tier or request a quota increase from the workspace admin with a written usage justification; without it, batch the work or shed load at the producer. Replay the failing scenario against a fresh test workspace at half the throughput to confirm the new safe rate before pushing to the real workspace.

Automate this fix so you do not do it twice

Multi-workspace rate-limit + retry policy via shared client wrapper

When the Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 integration runs across multiple workspaces or accounts, every consumer needs the same backoff, jitter, and idempotency behavior or one noisy workspace will starve the rest. Wrap the vendor SDK or fetch call in a thin client that reads the rate-limit headers (X-RateLimit-Remaining, Retry-After, x-ratelimit-reset), applies full jitter (base 200ms, cap 30s, max 5 retries), and de-dupes writes by a stable key (the platform's run id, the connector's external id, the destination record id). Emit simple log lines tagged with the workspace id so a quota burst on one workspace shows up in the same log as the downstream cascade.

# Python - power API wrapper with full-jitter retry
from tenacity import retry, wait_random_exponential, stop_after_attempt, retry_if_exception_type
import requests class RateLimited(Exception): pass @retry( wait=wait_random_exponential(multiplier=0.2, max=30), stop=stop_after_attempt(5), retry=retry_if_exception_type(RateLimited),
)
def call_power(method, path, token, payload=None): r = requests.request(method, f"https://api.example.com{path}", headers={"Authorization": f"Bearer {token}"}, json=payload, timeout=10) if r.status_code == 429: raise RateLimited(r.headers.get("Retry-After")) r.raise_for_status() return r.json()

Automate Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 session + sharing-policy snapshots via vendor CLI or API

On the Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026, regular session and policy snapshots catch silent role changes, sharing-default drift, and stale OAuth grants well before the workflow starts failing in prod. Pair vendor health checks (the platform's admin SDK, the platform's users API, the connector listing) with a token-validity check so both vendor-side and account-side issues land in one folder. Run the scheduled task on a control plane device (a small VPS, a GitHub Actions runner, a Cloud Function) under a tightly scoped service account that mirrors the real workspace policy.

# List workspace members + roles
curl -H "Authorization: Bearer $PLATFORM_TOKEN" \ https://api.example.com/v1/workspace/members \ > power-members.json
# List active connectors + their last-tested timestamp
curl -H "Authorization: Bearer $PLATFORM_TOKEN" \ https://api.example.com/v1/connectors \ > power-connectors.json
# Validate the bearer token itself
curl -H "Authorization: Bearer $PLATFORM_TOKEN" \ https://api.example.com/v1/me \ > power-me.json

Scrape Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 workspace audit log + integration log via scheduled job

For the Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026, workflow faults usually surface as failed run executions, audit-log denials, or quota nags before a full hang. A weekly scheduled job that exports the last 7 days of these events to CSV gives you a paper trail to correlate with platform updates, policy changes, and vendor incidents without staring at the settings panel live. Register the task via cron (Linux / macOS), Windows Task Scheduler (schtasks /create /XML), or a GitHub Actions schedule, then write the CSV to Dropbox / OneDrive / Google Drive for retention. Subscribe a simple dashboard (Google Sheets with a daily import, Airtable scheduled sync, Notion database via the API) to the same bucket so audit events from every Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 workspace converge on a single view without per-workspace clicking.

# Export the platform audit log via the API (Enterprise plan)
curl -X POST https://api.example.com/v1/audit_logs \ -H "Authorization: Bearer $PLATFORM_TOKEN" \ -H "Accept: application/json" \ -d '{"start_date":"2026-05-24","end_date":"2026-05-31"}' \ -o power-audit-log.json
# Export the run history for the last 7 days
curl -G https://api.example.com/v1/runs \ -H "Authorization: Bearer $PLATFORM_TOKEN" \ --data-urlencode "oldest=$(date -d '7 days ago' +%s)" \ -o power-runs.json

Pitfalls

Platform auto-updates during an active failure are the textbook way to break a Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 workflow further, and the trap catches experienced builders because the release notes look like they describe exactly the bug at hand. Never accept a major platform version bump while you are in the middle of debugging, never push a beta build unless the release notes tie it to a specific advisory for your symptom, and never roll forward when a rollback is available. Skipping a required workspace-policy migration leaves a known regression path open even after the immediate fix, so check the deprecation timeline on the Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 changelog before deciding to wait.

The other half is trusting the vendor status page verdict by itself. Vendor status pages can miss regional incidents that only hit one POP, the Trust Center will not flag a connector degradation, and the activity feed entries can lag several minutes behind the actual failure. Cross-reference the vendor X/Twitter status handle, Downdetector, the failing screenshot timestamps, and the on-screen symptom narrative before committing to a destructive remediation on Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026.

Full fix path

• Reproduce the original failing run against Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 on the same device AND a second device with the same account. If the failing toast or error code still surfaces on any device, you have not fixed it.
• Watch for 24 to 48 hours via the Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 workspace audit log + the integration history + your personal notes. Cached error states and CDN caches mask slow-burn drift and intermittent regional issues.
• Smoke-test under realistic load: replay the workflow against a test workspace for at least 30 minutes at your normal working pace, log success / error and the timestamp per attempt to a notes file.
• Capture the new state in a personal notes entry so the next time this happens you do not rediscover it. Note platform version + workspace policy + connected-apps list + failing screenshot + verbatim error string + fix applied. Push to a shared team wiki if your team uses one.
• If the fix involved an API token rotation or a workspace policy change, commit the new token to your password manager and screenshot the workspace settings for archival.

Safety, rollback, blast radius

• Test in a Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 test workspace or on a duplicate scenario first before any change that touches the real workspace. Snapshot the platform version, the workspace settings, the connected-apps list, and the sharing policy before changing anything.
• Apply the principle of least surprise when granting share access or connected-app permissions. Review the share list against the people who actually need access - extra shares are extra blast radius.
• Use idempotent runs where the Power Automate SharePoint Connector, Lists, Libraries, Permissions & Lookups, 2026 API supports it (the platform's run id de-dupe, external id keys on destination records) so a retried run does not create duplicate records.
• Know your rollback path. Platform version rollback is a one-line download-and-install; an API token rotation is reversible if you kept the old token in the password manager during cutover; a workspace policy change is reversible only if you saved the previous policy in a screenshot.
• For team-wide or workspace-wide changes, line up a maintenance window with team notification before pushing through the admin console.

FAQ

Related fixes

Related guides worth a look while you sort this one out:

• how to detect a connector timeout and fall back to a secondary HTTP endpoint inside the catch Scope
• how to call Grant access to an item or a folder action and email a recipient with a custom message
• how to set Concurrency Control on Apply to each to avoid SharePoint connector throttling
• how to send the run URL to admins via concat with environment().properties.endpoint in the catch
• how to use Do until with limit count and timeout to retry a polling HTTP call without infinite loop
• how to detect a SharePoint trigger not firing on subfolder events and use the folder path filter