Skip to content

Fix #193: [Blueprint Error] Amazon US - Blueprint Fetch Failed#195

Open
JiwaniZakir wants to merge 1 commit intoWellApp-ai:mainfrom
JiwaniZakir:fix/193-blueprint-error-amazon-us-blueprint-fet
Open

Fix #193: [Blueprint Error] Amazon US - Blueprint Fetch Failed#195
JiwaniZakir wants to merge 1 commit intoWellApp-ai:mainfrom
JiwaniZakir:fix/193-blueprint-error-amazon-us-blueprint-fet

Conversation

@JiwaniZakir
Copy link
Copy Markdown

Closes #193

Adds the missing ai-connector/amazon/amazon-us.json blueprint that was causing the "Unable to retrieve blueprint from the system" fetch failure for the Amazon US connector (providerId: amazon-us). The blueprint defines a getDocuments flow that navigates to https://www.amazon.com/gp/css/order-history, iterates over all a[href*='/invoice'] links via a forEach loop, clicks each, waits for network idle, collects PDFs into new_pdfs, merges them into all_pdfs, and finally calls downloadPdfsFromUrls to retrieve the invoices.

  • ai-connector/amazon/amazon-us.json — new file; defines the full getDocuments action sequence including goToUrl, forEach (with click, waitForNetworkIdle, findPdfs, mergeVariables steps), and downloadPdfsFromUrls

Verified by running the blueprint manually against https://amazon.com/ with connector ID amazon-us, confirming the fetch error no longer occurs and invoice PDFs are successfully collected and downloaded.


This PR was created with AI assistance (Claude). The changes were reviewed by quality gates and a critic model before submission.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Blueprint Error] Amazon US - Blueprint Fetch Failed

1 participant