The usual CCK lifecycle goes something like this.

1. Admin creates a new content type (e.g., FoobarPage)
2. Admin adds fields and specifies the datatype and the gui widgets for the fields and so forth
3. Admin saves the content type and determines permissions

4. User gets permission to create FoobarPage(s)
5. User logs in and fills out the CCK-generated form to make FoobarPages
6. User saves the FoobarPages and Drupal stores them as nodes
7. User navigates to the URL for the newly created nodes and looks at them as usual

===

Question: Does a module exist that changes the CCK lifecycle so that, at step
six for example, the user input to the form could actually get re-channeled to a
different destination other than the node table?

In other words, the user presses "save" ... but instead of creating a new node, the
data populated in the CCK form gets sent to a flat file on the server, or the
data gets sent to a different website that accepts the CCK contents via POST
parameters, or the data gets sent to *both* create a new node and also to an
alternate output destination.

===

Rationale: Ordinarily, one could use a module like "webform" to get the desired
outcome, but for various reasons, I would like to stick to using CCK with 're-channeled'
output instead.