The basic jist is to put Complice intentions in WorkFlowy, and then tag them with the date that you want them to show up in your intentions draft. You can fetch them using a button next to your intentions box that looks like this:
The "pull from workflowy" action will get automatically triggered after you submit your outcomes, to pull in intentions for the next day.
When you submit your intentions, the tasks are linked to workflowy, and checking off the task in Complice means it'll be marked done in WorkFlowy too.
If it seems to not be working, re-read this guide before contacting support. Usually it's due to a typo in the format, not a software bug.
#today and #tomorrow. If you tag something #today, it will get pulled whenever you press fetch. If you tag something #tomorrow, it will get pulled only when you're first setting your intentions, i.e. your list is empty (this fetch is automatically triggered when you submit your outcomes).
#tuesday and #2016-07-01. If you tag something with a day of the week, it will get pulled on that day. If you don't do it that day, it'll get pulled again the following week. You can also tag a task with a specific date in YYYY-MM-DD format. That task will only get pulled in on that day; if you miss it, Complice will forget about it.
Add #nolink to the WorkFlowy node, and it will pull it in but not link the Complice intention with the node (so eg. if you complete it it won't tell WorkFlowy)
Use #repeat instead and it'll link it but still won't tell WorkFlowy to complete the task. The difference is that by linking it you get a little button to click through to the node. This could be good if you want to do some reading from a list every day:
However, you probably won't need to use the #repeat tag very often, because there's usually a shorthand way to represent it.
You can stick an 's' on the end of days-of-the-week to make a task repeating as well! So #mondays is equivalent to #monday #repeat.
Is it Friday and you want to tag a work task for tomorrow, but not have it show up until Monday? Use #weekday. The reverse? Tag it #weekend. The "stick an 's' on the end to make a task repeat" trick works here too. So if something's part of your monday-friday routine, tag it #weekdays.
Monthly repeats: You can use #every15 and it'll make a repeating task on the 15th of every month. Note that #every30 will miss February, as it just checks if the day number is correct. But you can use #everylast for that!
And, just so you don't have to check: for one-digit days, leading zero is optional: both #every1 and #every01 will work.
Another common pattern is something like "first sunday of every month". This is supported as #firstsundays, and there's also #secondtuesday or #lastfridays. Note that while repeating dates are more typical here, you still do need to use a #repeat tag or an 's' on the end for it to repeat, just to maintain consistency.
Yearly repeats: Want to do something on a particular day every year? There's now something for that too! Both #everyyear-03-15 and #everyyear-day74 will cause an event to get pulled in every March 15th (exception: the second one will be on March 14th during leap years). January 1st is day 1.
Every other day: There are a few ways to do this. If you want it to be very strictly every other day, you'll probably want to use day-of-year tags. This will still break when the year ticks over (unless it's a leap-year) but mostly will be consistent. For this, use #doy-odd or #doy-even. For example, January 2nd is an even day of the year, and December 31st is (usually) day 365 so it's an odd day of the year. If you'd like to be better able to predict where it'll fall, use the day-of-month tags: #dom-odd or #dom-even. These work pretty intuitively: April Nth is odd if and only if N is an odd number. Same for every month. Pick odd to sometimes get 2 days on in a row; pick even to sometimes get 2 days off in a row (eg after July 31st comes another odd day, August 1st).
Be careful with these, as they can very easily clutter up your intentions with things you aren't actually planning to do, leading to major staleness.
This is designed to be really powerful, and to avoid cluttering up your WorkFlowy too much.
Say you want to sort some tasks into today, some into tomorrow, some into a backlog... the easiest way to do that is to drag, not to tag them all individually. So you can!
Use the #CG1 tag to indicate that all of the children of a given node are towards goal 1. Then you don't need to use the complice
1) format, you can just tag them with a date and you're good to go. (Use
#CG& for misc tasks. It works even though workflowy doesn't recognize it as a tag. Or #CG_)
(Note: you need to use either the #CG1 notation or the complice
1) format for something to get pulled from WorkFlowy. Otherwise Complice can't be quite certain that you want it.)
Also, it used to be that these goal tags didn't get updated when you renumbered your goals, but as of 2018-12-21, they do! But items using complice format still don't get fixed when you renumber, because many people use the same format just to make a numbered list.
Say you have a bunch of articles to read. You might want your intention to say e.g. "5) read malcolmocean.com/2016/06/you-flow-downhill/", but in workflowy, you want it to just be a list of urls. Well, that's possible! Put : around text on a parent and it'll get prepended to the node's immediate children. Note that the colon (:) is part of it!
There's a :[postfix]operator too, so you can have a parent node called notes to [integrate]::[into main model] and then a child called "convo notes with Sarah" becomes eg "1) integrate convo notes with Sarah into main model", with a link to the convo notes node—super convenient if the notes are on that node.
Prefix and postfix both only work with the #CG1-style pull, because otherwise Complice is just directly fetching the node and doesn't see what its parents are.
You might think you could do something like the example below, but it won't work. Can you see why?
The problem is that there's ambiguity about what's intended to be a task. Maybe "tasks for" is the task, and the things underneath are notes on it. If you do it like this, it will try to pull in the "tasks for #today" task, not the children individually.
Instead, the solution is to put the date tag as a prefix. So it's as if all of the children of that node have their own little #today tag, and they all get pulled in separately:
One thing you might not know about the internet is that you can style any website however you want.
If you're logged in, this section will show custom CSS for your goal colors.