English

Adding Forms, Uploads, Email & Payments

Describe the workflows behind forms, file uploads, email, and payments so condoo.Vibe connects your app to real, real-world outcomes.

Modern applications do more than display information.

They collect data, accept files, send messages, process payments, and trigger actions based on what users do.

With condoo.Vibe, you can describe these workflows in natural language and have your AI product team build the functionality into your application.

Don't just describe the interface. Describe what should happen.

Build the workflow, not just the screen

condoo.Vibe Form

Consider this prompt:

Add a contact form with name, email, phone number, and message.

That tells condoo.Vibe what the form should look like.

But what should happen after someone submits it?

A stronger request is:

Add a contact form with name, email, phone number, and message. Save every enquiry to the database, show it in the admin dashboard, send a confirmation email to the customer, and notify our team when a new enquiry arrives.

Now you're describing a complete workflow:

Customer submits form
        ↓
Validate information
        ↓
Save enquiry
        ↓
Show in dashboard
        ↓
Send confirmation
        ↓
Notify team

condoo.Vibe can build the different pieces required to make that workflow work.

Forms

Forms allow users to send information into your application.

They can be used for:

You can describe the information you want to collect and what should happen afterward.

Creating a form

For example:

Add a lead capture form with name, work email, phone number, company name, company size, and message. Name and email are required.

condoo.Vibe can create the appropriate fields, validation, and interface.

But for a real application, you should also describe what should happen to the submission.

For example:

Save every submission as a lead in the database and show new leads in the sales dashboard.

Now the form is connected to your application.

Form validation

Validation determines what information is acceptable before a form is processed.

For example:

Name and email are required. Validate that the email address is correctly formatted and show an inline error beneath invalid fields.

Or:

Passwords must contain at least 8 characters.

Or:

The booking date cannot be in the past.

condoo.Vibe can implement validation around the requirements you describe.

A useful prompt includes both:

What information is required

and

what makes that information valid.

Success and error states

Don't forget what happens after submission.

For example:

After successful submission, clear the form and show a success message saying "Thanks! We'll get back to you shortly."

Also consider failure:

If submission fails, keep the user's entered information and show an error message with an option to try again.

Good application experiences account for both outcomes.

File Uploads

Some applications need users to upload files.

Examples include:

You can describe the upload experience you want.

For example:

Allow real estate agents to upload multiple images when creating a property listing. Display the images in a gallery on the property detail page.

Or:

Allow customers to attach PDF, DOCX, JPG, and PNG files to support tickets.

Describe upload restrictions

For uploads, tell condoo.Vibe about any important restrictions.

For example:

Allow up to 10 property images per listing. Accept JPG, PNG, and WebP files and limit each file to 10 MB.

Or:

Only accept PDF documents up to 20 MB.

This gives condoo.Vibe clearer requirements for validation and user feedback.

File storage

Files generally shouldn't be stored directly inside your application's relational database.

Instead, applications commonly use dedicated media or file-storage services and store references to those files in the database.

condoo.Vibe supports connectors such as Cloudinary for workflows involving media storage and delivery.

For example:

User selects image
       ↓
Application validates file
       ↓
Image uploaded to Cloudinary
       ↓
File reference saved
       ↓
Image displayed in application

We'll cover Cloudinary setup in detail in the Integrations section.

Email

Applications frequently need to send emails based on user actions.

Examples include:

condoo.Vibe can build email workflows using supported email integrations such as Resend.

Describe when an email should be sent

Instead of simply saying:

Add email.

Describe the event.

For example:

When a customer successfully books an appointment, send them a confirmation email containing the service, staff member, date, time, and booking reference.

That's much clearer.

Conceptually:

Booking created
      ↓
Save booking
      ↓
Send confirmation email
      ↓
Display success state

Send emails to your team

Email isn't only for customers.

For example:

When someone submits the demo request form, save the lead and email our sales team with the person's name, email, company, and message.

Or:

Notify the assigned agent whenever a new lead is assigned to them.

condoo.Vibe can connect application events to email workflows.

Connect Resend

For applications that send transactional emails, you can connect Resend through condoo.Vibe's supported integration flow.

Once configured, you can focus your prompts on what should happen.

For example:

Send a welcome email after registration.

Rather than manually implementing the entire email delivery workflow yourself.

We'll walk through connecting Resend later in the Integrations section.

Payments

You can also build payment experiences into your application.

condoo.Vibe supports Stripe for payment workflows.

This allows you to build experiences such as:

You describe how payments should fit into your product.

One-time payments

For example:

Customers should be able to purchase this digital course for $99 using Stripe. After successful payment, give the customer access to the course dashboard.

This involves more than displaying a payment button.

Conceptually:

Customer chooses product
        ↓
Stripe checkout
        ↓
Payment succeeds
        ↓
Application verifies payment
        ↓
Access granted

condoo.Vibe can build the application workflow around the payment process.

Subscription payments

For SaaS applications, you might need recurring subscriptions.

For example:

Add three subscription plans: Starter at $19/month, Pro at $49/month, and Business at $99/month. Users should choose a plan during checkout and their account should reflect their active subscription afterward.

For more sophisticated billing systems, you may also need:

For these cases, consider using Plan Mode before implementation.

Payments are more than checkout

A common mistake is thinking that adding Stripe means simply creating a checkout page.

A real subscription workflow may look more like:

User selects Pro
       ↓
Checkout created
       ↓
Stripe processes payment
       ↓
Payment confirmed
       ↓
Subscription recorded
       ↓
Pro features unlocked
       ↓
Dashboard updated

Your application needs to know what happened after the user leaves Stripe.

That's why payment workflows often involve both Stripe and your application's backend.

Combine capabilities into workflows

The real power comes from combining these capabilities.

Imagine you're building a photography booking platform.

You could tell condoo.Vibe:

Customers should complete a booking form, choose a photography package, upload reference images, pay a 30% deposit through Stripe, and receive a confirmation email after successful payment. Save the booking in the admin dashboard with a "Deposit Paid" status.

That single product workflow involves:

Form

Collect booking details.

↓

Upload

Store reference images.

↓

Stripe

Collect the deposit.

↓

Database

Save the booking and payment state.

↓

Resend

Send confirmation.

↓

Dashboard

Show the booking to the photographer.

You're describing the customer experience.

condoo.Vibe can help build the systems behind it.

Another example: Lead qualification

Suppose you're building an agency website.

You could ask:

Create a "Request a Proposal" form. Ask for name, company, email, website, monthly marketing budget, services needed, and project description. Save submissions as leads. If the budget is above $5,000, mark the lead as High Priority and notify the sales team by email.

Conceptually:

Proposal submitted
        ↓
Save lead
        ↓
Check budget
        ↓
   Above $5,000?
      ↙       ↘
    Yes        No
     ↓          ↓
High Priority  Standard
     ↓
Notify sales

This is application logic created around a form.

Describe the complete outcome

When prompting condoo.Vibe, think beyond the visible component.

Instead of:

Add an application form.

Try:

Add an application form collecting name, email, LinkedIn profile, years of experience, role, and CV. CV should accept PDF files only. Save applications in the database and show them in the admin dashboard. Send the applicant a confirmation email after successful submission.

Instead of:

Add a Buy button.

Try:

Add a Buy button that starts Stripe checkout. After successful payment, record the purchase and unlock the customer's download inside their account.

The more clearly you describe the outcome, the better condoo.Vibe can understand the complete workflow.

External services require connectors

condoo.Vibe can build the application logic around external services, but those services still belong to their respective providers.

For example:

Capability Service
Payments Stripe
Transactional email Resend
Communications Twilio
Media Cloudinary

You'll generally need to connect the appropriate account or credentials before the application can use that external service.

condoo.Vibe's Connectors make this process easier.

We'll cover each supported connector individually later.

Keep credentials secure

External integrations frequently require API keys or other credentials.

These values should be treated as secrets.

Use condoo.Vibe's supported connector or secure configuration flows when adding credentials.

Once connected, your prompts can focus on the product behavior rather than repeatedly supplying credentials.

Choose the right mode

Simple workflows can often go directly to Build Mode.

For example:

Add a contact form and save submissions to the database.

Build + Min may be sufficient.

More complex workflows deserve planning.

For example:

Add subscriptions with three plans, feature limits, upgrades, downgrades, cancellations, failed-payment handling, and a customer billing portal.

Consider:

Plan + Max → Review → Build

This allows condoo.Vibe to reason through the complete billing architecture before implementation.

Example prompts

Contact form

Create a contact form with name, email, company, and message. Save submissions and show a success message afterward.

Upload

Allow users to upload a profile image. Accept JPG, PNG, and WebP and show the uploaded image on their profile.

Email

Send customers an email confirmation after successfully booking an appointment.

Payment

Add Stripe checkout for the Pro plan at $49/month and update the user's subscription after successful payment.

Complete workflow

Build a consultation booking flow. Customers should choose a service, select an available date and time, enter their contact details, pay the consultation fee through Stripe, and receive an email confirmation. Save the booking and payment status in the database.

Think in outcomes

You don't need to tell condoo.Vibe every technical step required to implement a workflow.

Start with:

What should the user be able to do?

Then:

What should happen when they do it?

And finally:

What information should the application remember?

For example:

That's a product workflow.

condoo.Vibe can help turn it into working software.

Next: APIs and Server-Side Logic

Forms collect information.

Databases store it.

Integrations connect your application to external services.

But something still needs to determine what happens when users perform actions.

Next, we'll look at APIs and Server-Side Logic: the functionality behind your application's buttons, workflows, permissions, calculations, and integrations.

APIs and server-side logic

See how condoo.Vibe builds the logic behind buttons, workflows, and integrations.