Adding Conditions in the UI
You understand what conditions are and how they work. Now let's walk through exactly how to add them in the Taibles interface, step by step.
Opening Column Configuration
Before you can add a condition, you need to access the column settings.
Method A: When Creating a New Column
Starting fresh with a new column:
Click "Add Column" in the top right →
- Click "Add Column" in the top right of your taible
- Choose your column type from the categories (e.g., "Clearbit Enrichment" from CRM & Sales)
- Configuration modal opens automatically on the right side
You're ready to add conditions! ✓
Method B: Editing an Existing Column
Modifying a column you've already created:
Hover over the column name to see the menu →
- Find your column in the taible grid
- Hover over the column name at the top
- Click the three-dot menu (⋮) that appears
- Select "Configure column" from the menu
- Configuration modal opens on the right
You're ready to add conditions! ✓
Finding the Condition Setting
The configuration modal has multiple tabs. Here's where conditions live:
Column-Specific Settings
Settings like API accounts, method selection, and input parameters appear here.
Click "Run Configuration" to access condition settings →
Tab Structure
The modal shows two main tabs:
- Data Configuration - Settings specific to your column type
- Run Configuration - When and how the column runs (this is where we're going!)
Click the "Run Configuration" tab to find the condition setting.
The Run Configuration Panel
Inside the Run Configuration tab, you'll see several settings:
Run Configuration
← This is where you'll add your condition
The condition editor is at the bottom of the Run Configuration panel
Condition settings are at the bottom, with the question:
"Do you want this column only to run when a condition matches?"
Below this question is the condition editor where you'll write your rules.
Adding Your First Condition
Let's add a simple condition step by step.
Example Scenario: Only Enrich Valid Emails
Goal: Skip enrichment when the email address is invalid
The condition we'll create: Only run when the "email_valid" column equals true
Step 1: Click in the Condition Editor
To access data from other columns, press CTRL + SPACE or start typing the column name.
- Scroll down to "Do you want this column only to run when a condition matches?"
- Click in the editor field below the question
- The editor is now active and ready for input
Step 2: Start Typing
Begin with your column name:
Type the first few letters of the column you want to check.
As you type, autocomplete shows matching columns and system variables
As you type:
- An autocomplete menu appears
- Shows all available columns from your taible
- Displays special system variables (like "Now", "Today", "1 Hour Ago")
- Each option shows its data type (text, number, true/false, etc.)
Helpful hint: Press CTRL + SPACE at any time to open the autocomplete menu
Step 3: Select Your Column
Three ways to select:
Three Ways to Select
Option A: Keep typing until your column is highlighted, then press Enter
Option B: Use arrow keys (↓↑) to navigate, then press Enter
Option C: Click the column name in the dropdown
Result: The system inserts the column reference automatically
Step 4: Complete Your Condition
Add the comparison:
What you typed: Selected "Email Valid" from autocomplete, then typed "equals true"
Continue typing to complete your condition:
[email_valid] equals trueAs you type:
- The editor shows [Column Name] in a green badge
- Your condition appears in plain, readable text
- No complex syntax to memorize - just natural comparisons
Step 5: Review and Save
Double-check your condition:
Review Checklist
Common Mistakes to Avoid:
Right: [status] equals "active"
Make sure:
- ✅ Column name is correct
- ✅ Comparison makes sense (equals, greater than, etc.)
- ✅ Your condition will evaluate to true or false
Common checks:
- Text comparisons need quotes:
[status] equals "active" - Numbers don't:
[count] greater than 5 - True/false values:
[verified] equals true
Step 6: Save the Column
Click "Save Column" to apply your changes →
- Scroll to the bottom of the configuration modal
- Click the "Save" button (usually blue/primary color)
- Success message appears (green notification)
- Modal closes
Your condition is now active! ✓
Testing Your Condition
After saving, test with real data to verify it works as expected.
Best Practice: Test Before Processing Everything
Recommended Testing Workflow
Recommended approach:
- Save your column configuration
- Manually run 2-3 test rows
- Check that some rows execute and others skip
- Once confirmed, let automatic processing take over
Watching Conditions Work in Real-Time
Let's see what happens when conditions evaluate.
Scenario 1: Condition is True (Should Run)
When the condition passes:
Cell State Progression
- Green "Completed" badge
- Your data is visible in the cell
- Click to see full details
You'll see the cell progress through states:
- Ready (gray) → Waiting to start
- Queued (pulsing clock) → In line to run
- Running (spinning gear) → Currently processing
- Completed (green badge) → Done successfully
Cell shows:
- ✅ Green "Completed" badge
- Your data is visible in the cell
- Click the cell to see full details
Scenario 2: Condition is False (Should Skip)
When the condition doesn't pass:
When Condition Fails
What this means:
The cell shows:
- Gray muted text: "Skipped (Condition failed)"
- Special icon (⌥) before the text
- No data processing happened
- Previous data preserved (if any existed)
What this means:
- ✅ The system checked your condition
- ✅ It evaluated to false (didn't match)
- ✅ No API calls were made (saved money!)
- ✅ No processing happened (saved time!)
- ✅ Other columns can still run if they need to
Understanding Skipped Cells
Understanding Skipped Cells
Why was it skipped?
What actually happened:
Why was my cell skipped?
Look at the inline display in the cell:
- Shows "Skipped (Condition failed)"
- Includes when the condition was checked
- Previous cell data remains unchanged
What actually happened:
- Your condition was evaluated
- It returned false (not true)
- The system skipped processing
- No resources were consumed
This is working correctly! The condition did its job - it prevented unnecessary work.
Editing Existing Conditions
To modify a condition after saving:
Step 1: Reopen Configuration
Reopening Configuration
Hover and click menu (⋮) →
- Hover over column header
- Click three-dot menu (⋮)
- Select "Configure column"
- Click "Run Configuration" tab
Step 2: Modify the Condition
Modifying an Existing Condition
- Scroll to the condition editor
- Your existing condition is displayed
- Click in the field to edit
- Make your changes (add, remove, or modify)
Example modification:
Original:
[email_valid] equals trueModified to include size check:
[email_valid] equals true AND [company_size] greater than 50Step 3: Save Changes
- Review your updated condition
- Click "Save" at the bottom
- Condition updated ✓
What happens to existing cells:
- Cells already completed → Stay completed (won't change)
- Cells not yet run → Use the new condition
- Cells that were skipped → Still skipped (won't auto-rerun)
To reprocess with the new condition:
- Select the rows you want to reprocess
- Right-click → "Re-run selected cells"
- Cells evaluate with your new condition
Removing Conditions
To remove a condition and always execute:
Removing a Condition
Click in the field and select all (Ctrl/Cmd + A) →
Steps:
- Open column configuration
- Go to Run Configuration tab
- Find the condition editor
- Select all text (Ctrl/Cmd + A)
- Delete (Backspace or Delete key)
- Field is now empty
- Click "Save"
Empty condition = Always execute (no filtering)
Visual Guide to the UI
The Condition Editor
Condition Editor Features
Key features you'll see:
- Column references appear as green badges
- Autocomplete triggered by CTRL + SPACE or just typing
- System variables available (Now, Today, dates, etc.)
- Visual formatting makes conditions readable
- No validation errors shown upfront - you'll see them when cells run
Helpful hint below the editor:
"To access data from other columns, press CTRL + SPACE or start typing the column name."
Cell State Indicators
Cell State Visual Reference
| State | Visual | What It Means |
|---|---|---|
| Ready | Gray text | Waiting to start |
| Queued | Pulsing clock | In line to run |
| Running | Spinning gear | Currently processing |
| Completed | Completed | Successfully finished |
| Skipped | Skipped (Condition failed) | Condition failed - skipped |
| Rate Limited | Rate Limited | Waiting due to rate limits |
| Error | Unsuccessful | Something went wrong |
What you'll see in cells:
| State | Visual | What It Means |
|---|---|---|
| Ready | Gray text | Waiting to start |
| Queued | Pulsing clock icon | In line to run |
| Running | Spinning gear | Currently processing |
| Completed | Green badge | Successfully finished |
| Skipped | Gray italic with ⌥ | Condition failed - skipped |
| Rate Limited | Yellow pause icon | Waiting due to rate limits |
| Error | Blue "Unsuccessful" badge | Something went wrong |
Keyboard Shortcuts
Speed up your workflow with these shortcuts:
In the Condition Editor
| Shortcut | Action |
|---|---|
| CTRL + SPACE | Open autocomplete menu |
| ↓ ↑ | Navigate suggestions |
| Enter | Select highlighted item |
| Esc | Close autocomplete |
| Tab | Move to next field |
| Ctrl/Cmd + S | Save configuration |
Troubleshooting Common UI Issues
Issue 1: "Can't Find the Condition Setting"
Symptoms: Don't see "Do you want this column only to run when a condition matches?"
Can't Find the Condition Setting
Possible causes:
- Wrong tab - Make sure you're on "Run Configuration" tab (not "Data Configuration")
- Need to scroll - The condition setting is at the bottom of the panel
- Manual column - Manual input columns don't have conditions (they're user input, not calculated)
Solution:
- Click the "Run Configuration" tab
- Scroll all the way down
- Verify this isn't a manual input column
Issue 2: "Autocomplete Not Appearing"
Symptoms: Type but no suggestions appear
Autocomplete Not Appearing
Solutions:
- Click in the editor first - Make sure the cursor is active
- Press CTRL + SPACE - Manually trigger autocomplete
- Wait a moment - May take 1-2 seconds to load
- Refresh if needed - If columns were just added, refresh the page
Issue 3: "Can't Save Configuration"
Symptoms: Click "Save" but nothing happens
Can't Save Configuration
Check for:
- Column name empty - The name field must be filled in
- Required fields missing - Check for any red error messages
- Save button disabled - Hover over it to see why
- Network issue - Check your internet connection
Best Practices for the UI
✅ Do This
Best Practices: Do This
1. Use Autocomplete
- Press CTRL + SPACE frequently
- Prevents typos in column names
- Shows you what's available
- Displays data types
2. Test Incrementally
- Save and test on 2-3 rows first
- Don't process thousands untested
- Verify skipping works correctly
- Check that execution works correctly
3. Review Before Saving
- Double-check column names
- Verify comparison operators
- Confirm the logic makes sense
- Think through example scenarios
4. Start Simple
- Begin with basic conditions
- Test and verify behavior
- Add complexity gradually
- Build on what works
❌ Avoid This
Best Practices: Avoid This
1. Don't Skip Testing
- Never save and immediately process all rows
- Conditions might not work as expected
- Always test on sample data first
2. Don't Type Everything Manually
- Use autocomplete to prevent typos
- A misspelled column name will fail at runtime
- Let the system help you
3. Don't Forget to Save
- Changes aren't applied until you click "Save"
- Closing the modal discards unsaved changes
- No warning is shown for unsaved state
4. Don't Edit in Production Without Testing
- Test on duplicate taibles if possible
- Or test on a few rows first
- Errors only show up at execution time
Summary: What You Can Do Now
You've learned how to use the UI to add conditions:
✅ Open Configuration
- Create new columns with conditions
- Edit existing column conditions
- Navigate the configuration modal
✅ Add Conditions
- Find the condition editor in Run Configuration
- Use autocomplete (CTRL + SPACE)
- Write natural comparisons
- Conditions validated at runtime
✅ Test and Verify
- Save your configuration
- Test on sample rows
- Watch cells execute or skip
- Understand visual indicators
✅ Monitor Execution
- Recognize all cell states
- Understand "Skipped (Condition failed)"
- See which rows executed vs. skipped
- Track progress visually
✅ Modify and Remove
- Edit existing conditions
- Remove conditions to always execute
- Reprocess rows with new conditions
- Understand impact on existing cells
✅ Troubleshoot
- Find the Run Configuration tab
- Trigger autocomplete manually
- Verify all required fields
- Check save button status
Next Steps: Real-World Examples
Now that you know what conditions are (Section 5.1) and how to add them in the UI (Section 5.2), Section 5.3 will show you:
- Complete business automation examples
- Cost-saving calculations
- Complex condition patterns
- Troubleshooting real scenarios
- Advanced tips and tricks
Let's see conditions in action with real business use cases! 🚀