The idea to converge the 4-Step Extract, Load, Transform, and Schedule sub-UIs into a single UI that is the current Schedules UI has been shared a lot. I seemingly have not created an issue so here it is. I recently made a video demonstrating the concept https://www.youtube.com/watch?v=Dr0_yUBWvWk Below is a snapshot of the hacked together rough idea I intend for this issue. The difference being Loader and Transform would be additional columns in the top "Add" section. Then from these dropdowns a list (vs. our current card UI approach) of our existing connectors would be displayed. The connector "Install" or "Configure" would popup the same modal configuration we have currently. - **Due to the video demo and below screenshot having a slightly different goal, the term "Datasets" was used where "Pipelines" would be the target term for this issue** - **The two sections (Add and Pipelines) in a single UI is the core goal**  Pros: - Simplified UI - Improved mental model (user feedback currently is that when setting up each connector it feels like a global setting where in this solution you're creating data pipelines where the connector settings are *for that pipeline*). Technically speaking the configurations (`Profile`s) will be reusable if desired per pipeline. Cons: - Existing users may dislike the change having gotten used to the current UI #### TODOS - [x] in-lining the "Create Pipeline" modal on the Pipelines page - [x] removing the "Extract" and "Load" steps - [x] making the "Extractor" and "Loader" dropdowns smarter, by having selection automatically trigger installation and/or configuration - [x] only listing extractors in the dropdown that don't already have a pipeline - [-] adding an Edit pipeline button and modal to modify the extractor configuration - We can add this later if needed, but I think we don't actually want editing of an existing configuration that's tied to a pipeline. This is because subsequent runs (after a modified configuration) could pollute/blend data from multiple accounts (configurations) into the same analytics db. @mbergeron Can you confirm or deny? - [x] 'Pipeline' -> 'Dataset' & 'Analyze' to 'Report' (routes and labels)