New Condition: Node is new

Can't you already this info without the action, according to the event you are using i.e. if it's an Insert or Update operation ?

I did comment on your other post #364173: Consolidate 'After saving new content' & 'After updating existing content' to 'Node is saved' :). Since fago said on my similar issue ;

hm, I don't think it's a good idea. If we start doing so, we could add events for a lot of possible combinations of events. So I think we need to find a more generic solution for this kind of improvement.

I assume this will be wont-fixed as well.

I like this condition, even without the combined event it's useful in several cases.

Consider passing the nodes from insert/update to a rule set or event "content is going to be saved", where the nid might be set or not.

@use case:
Really nice, perhaps you could share your rule here, once all patches are in? :)
http://drupal.org/node/298483

@code:
The condition should return a proper boolean, then !isset() is prefered instead of is_null(). Last I think it can be abbreviated to just

 return empty($node->nid) || !empty($node->is_new);

Then we should add a simple label callback for it, that replaces Content with the label of the used argument (%node).

FYI http://drupal.org/node/367387

I implemented the stuff I suggested in #4 and committed it.

If have have several events firing in the same hook, e. g. "Workflow state has changed" and "After updating existing content" in hook_nodeapi($op = 'update'), and changed the node in the first rule, the condition "Node is new" might not apply any more as the node has already been saved once. Therefore I suggest by comparing the $node->created and $node->updated timestamp as an additional possibility for identifying new nodes.

In my case it's better to patch the workflow module, please see http://drupal.org/node/1568864. Patch from comment #8 has a wrong logic and should be obsolete.

Does the rules module keep the $node->is_new flag after actions have modified a new node? In my opinion it should, otherwise subsequent events cannot properly interpret the node state..