You just picked up a list of eight properties from an auction, a wholesaler, or your own driving-for-dollars spreadsheet. Every one of them needs to become a project before you can run numbers on it.
So you sit down and type them in one at a time. Address, purchase price, close date, repeat. It is twenty minutes of work that produces nothing you did not already have written down, and it is the exact kind of task that gets postponed until the deal is already moving.
You give your assistant a spreadsheet, a pasted list of addresses, or even an email from your acquisitions team. It reads whatever structure is there and works out which column is the address, which is the purchase price, which is the target close date, and so on.
Before it creates anything, it checks your existing projects so it does not create a second copy of something you already have. Then it creates each project one at a time and reports back a list of what it made, along with anything it skipped and why.
What it will not do: this automation only creates new projects. It does not modify or archive existing ones. If an address already exists in your workspace, it will tell you rather than creating a duplicate.
I am giving you a list of properties to set up as FlipperForce projects.
Before you create anything:
1. Pull my existing project list and check for matches on address, so we do not create duplicates
2. Show me what you found and what you plan to create, and wait for me to confirm
Then for each new property, create the project using POST /workspace/{workspace}/project and fill in every field my list provides, including address, purchase price and any dates or notes.
When you are done, give me a table of what was created, what was skipped as an existing match, and anything you could not parse. Do not guess at missing values. Leave them blank and flag them so I can fill them in.
Name the endpoint explicitly when you use this prompt. Project creation sits at a different path from every other create route in our API, and an assistant left to search the specification on its own may conclude it is unsupported. The prompt above already includes the path for this reason.