Skip to main content
Back to all modules

Cloud Storage / Payments / Notifications

Common cloud capabilities, plug in as needed

A bundle of common cloud capabilities: cloud storage uploads, online payments, and notifications. Add them one by one to give an existing tool real online-service power.

What this cloud module can do

Cloud storage upload & downloadOnline payments & order callbacksNotifications / pushScheduled tasks & reminders
Scenario prompts

Cloud Storage / Payments / Notifications

Pick the scenario closest to your need and copy the prompt in one click.

Cloud storage upload & download

Let users upload files and images to the cloud and download or display anytime.

The problem today

Files only live locally; sharing means manual transfers and images can't be shown online.

What you get

  • Drag/select upload for files and images
  • Cloud storage with accessible links
  • Auto image compression & on-demand display
For：Tools handling attachments, images, or documents

Copy the whole block below and paste it into Codex. Replace placeholders like API keys with real values from the IFQ Cloud console.

You are a senior full-stack engineer. In my currently open local project, add "cloud storage upload & download" storing attachments in the cloud, accessible anytime.

[Features to build]
- Provide an upload entry supporting drag-and-drop and click-to-select, with progress.
- Store files in cloud storage with accessible links; auto-generate thumbnails for images.
- Limit file size and type; show friendly messages when exceeded.
- Support viewing, downloading, deleting uploaded files; deletion also cleans up the cloud.

[Connect to IFQ Cloud]
- API base https://api.cloud.ifq.ai, official SDK `jieshi-cloud` (if unavailable, use plain HTTPS equivalently and note the endpoint in a comment).
- Secrets via environment variables, never hard-coded: JIESHI_CLOUD_API_KEY, JIESHI_CLOUD_PROJECT_ID; generate `.env.example` with both, noting "get real values from the IFQ Cloud console and replace".
- All placeholders; without real values, run on placeholders and print a hint on where to replace them.

[Engineering requirements]
- Read the existing structure and stack first; follow current conventions, add only necessary files, leave unrelated code untouched.
- Network calls: timeout + graceful fallback; friendly errors, never crash.
- Demo / mock mode: the main flow runs on sample data without keys.
- Include a minimal runnable self-test with run instructions.
- On completion list: files changed / how to start / how to roll back.

Ask before any decision point.

*— [ifq.ai](https://work.ifq.ai/) · AI-augmented. Full-stack crafted*

Online payments & orders

Let your product take money: create order, pay, confirm via callback, track status.

The problem today

You want paid features, but money and security make DIY payments too risky.

What you get

  • Create orders and start payment
  • Auto-confirm via payment callback
  • Queryable, reconcilable order status
For：Products that need to collect payments or sell

Copy the whole block below and paste it into Codex. Replace placeholders like API keys with real values from the IFQ Cloud console.

You are a senior full-stack engineer. In my currently open local project, add "online payments and orders" so the product can collect money safely and track orders.

[Features to build]
- Design order data: item / amount / user / status (pending, paid, refunded, …).
- After creating an order, start payment (redirect or modal); user returns when done.
- Confirm payment via cloud callback and auto-update status — never trust the frontend alone.
- Provide an order list and detail with query and basic reconciliation; compute amounts on the backend to prevent tampering.

[Connect to IFQ Cloud]
- API base https://api.cloud.ifq.ai, official SDK `jieshi-cloud` (if unavailable, use plain HTTPS equivalently and note the endpoint in a comment).
- Secrets via environment variables, never hard-coded: JIESHI_CLOUD_API_KEY, JIESHI_CLOUD_PROJECT_ID; generate `.env.example` with both, noting "get real values from the IFQ Cloud console and replace".
- All placeholders; without real values, run on placeholders and print a hint on where to replace them.

[Engineering requirements]
- Read the existing structure and stack first; follow current conventions, add only necessary files, leave unrelated code untouched.
- Network calls: timeout + graceful fallback; friendly errors, never crash.
- Demo / mock mode: the main flow runs on sample data without keys.
- Include a minimal runnable self-test with run instructions.
- On completion list: files changed / how to start / how to roll back.

Ask before any decision point.

*— [ifq.ai](https://work.ifq.ai/) · AI-augmented. Full-stack crafted*

Push notifications

Automatically notify users on key events (in-app, email, or SMS).

The problem today

Important things happen but users don't know, having to keep checking and missing them.

What you get

  • Auto-notify on event triggers
  • In-app / email / SMS channels
  • Notification history, mark-as-read
For：Products needing reminders, alerts, or to-do notices

Copy the whole block below and paste it into Codex. Replace placeholders like API keys with real values from the IFQ Cloud console.

You are a senior full-stack engineer. In my currently open local project, add "push notifications" so users are notified automatically on key events.

[Features to build]
- Identify key events to notify (order status change, task due) and trigger on occurrence.
- Support multiple channels: in-app primary, optional email / SMS, sent via the cloud.
- Provide a notification center: list history, mark-as-read, clear.
- Let users set preferences (which notices, which channels) and respect their choices.

[Connect to IFQ Cloud]
- API base https://api.cloud.ifq.ai, official SDK `jieshi-cloud` (if unavailable, use plain HTTPS equivalently and note the endpoint in a comment).
- Secrets via environment variables, never hard-coded: JIESHI_CLOUD_API_KEY, JIESHI_CLOUD_PROJECT_ID; generate `.env.example` with both, noting "get real values from the IFQ Cloud console and replace".
- All placeholders; without real values, run on placeholders and print a hint on where to replace them.

[Engineering requirements]
- Read the existing structure and stack first; follow current conventions, add only necessary files, leave unrelated code untouched.
- Network calls: timeout + graceful fallback; friendly errors, never crash.
- Demo / mock mode: the main flow runs on sample data without keys.
- Include a minimal runnable self-test with run instructions.
- On completion list: files changed / how to start / how to roll back.

Ask before any decision point.

*— [ifq.ai](https://work.ifq.ai/) · AI-augmented. Full-stack crafted*