The Send to Story action allows you to send data to a sub-story where it can be further processed.

Sub-stories are special stories in Tines that can be used to perform a common action or set of actions. Use the Send to Story action to send data to an ‘analyse URL’ sub-story or a ‘deprovision user’ sub-story.

Features

  • Send event data to sub-stories where it can be processed.

Configuration Options

  • story: Provide the id of the sub-story to which data should be sent. Use the STORY widget {{ .STORY }} to easily find sub-stories in the tenant.
  • payload: Provide data that should be sent to the sub_story. Include information from upstream events by specifying a wrapped JSONPath.
  • send_payload_as_body: (Optional) True by default. When set to false, the payload emitted by the action is not nested under a body key.

Emitted Events

Events emitted by the Send to Story action will contain information returned by the sub-story’s exit action.

Example Configuration Options

Send a single URL to a sub-story to analysis. Use the story widget to locate the sub-story’s ID by name.

{
  "story": "{{ .STORY.analyse_url %}",
  "payload": {
    "url": "http://evil-site.net"
  }
}

When resolving the story name the system first looks in the current team, then for any stories that are globally enabled for send to story.

Send the same URL for analysis, but this time use the ID of the story.

{
  "story": 7,
  "payload": {
    "url": "http://evil-site.net"
  }
}