Skip to main content
Altcraft Docs LogoAltcraft Docs Logo
User guideDeveloper guideAdmin guide
Company siteHelp center
English
  • Русский
  • English
v73
  • v74
  • v73
  • v72
Login
  • Getting Started
  • Administrator documentation
  • Functional characteristics
  • Technology description
  • System requirements
  • Admin Panel
  • Platform installation
  • Platform configuration
  • Platform maintenance
  • Custom channels guide
    • Overview
    • Creating and configuring a channel
    • Entity field configuration
    • Template language
    • Entities
    • Pipes
      • Pipe: Basic Concepts
      • Result
      • Errors
      • Log
      • Pack
      • Unpack
      • HTTP Request
      • Store Set
      • Store Get
      • Selector
      • SQL
      • Eventer
      • Scheduler
    • Pipelines
  • Extra
  • Processing HTTP/HTTPS traffic
  • Administrator API
This is documentation for Altcraft Platform v73. This documentation is no longer maintained.
The information for up-to-date platform version at this page is available (v74).
  • Custom channels guide
  • Pipes
  • Eventer
Documentation for version v73

Eventer

Description​

Eventer The pipe registers a custom channel event. This pipe is also used to implement the moderation mechanism and stop the placement mailing on a channel with a configured Stop pipeline.

Structure​

FieldType of valueExampleRequiredDescription
idnumber10yesPipe's ID
typestring"event"yesType of a pipe
paramsEventParamsObject
noType-specific parameters
outsOutsObject
noPipe's outputs

EventParamsObject
FieldTypeExampleReqieredDefaultDescription
event_typestringsendyes-

Event type. The following options are possible:

  • stop
  • moderate_pass
  • moderate_error
  • send
  • deliv
  • sbounce
  • hbounce
  • complain
  • undeliv
  • reply
  • custom
channel_idint10001

yes,


beside event_type:

  • stop
  • moderate_pass
  • moderate_error
-Channel ID.
action_typeint100005

yes,


beside event_type:

  • stop
  • moderate_pass
  • moderate_error
-Channel ID.
eventEventObjectyes-Event Specific Parameters

EventObject
FieldTypeExampleReqieredDefaultDescription
send_message_id

string

$origin.send_message_idyes-

ID of the message in the platform.

caution

If we are talking about the Schedule pipeline, then the message identifier must additionally be transmitted using the Schedule pipe. In this case, it can be accessed will be received as follows:

$origin.<name of the field with the identifier from the Schedule pipe>

Errors​

  1. Error processing template params.event.send_message_id.

  2. params.event.send_message_id format is incorrect.

Example​

  1. {
    "id": 100,
    "type": "event",
    "params": {
    "event_type": "send",
    "channel_id": 10001,
    "action_type": 100021,
    "event": {
    "send_message_id": "$origin.send_message_id"
    }
    },
    "outs": {
    "error": 101
    }
    }
  2. {
    "id": 150,
    "type": "event",
    "params": {
    "event_type": "stop",
    "event": {
    "send_message_id": "$origin.send_message_id"
    }
    }
    }
  3. {
    "id": 18,
    "type": "event",
    "params": {
    "event_type": "moderate_error",
    "event": {
    "send_message_id": "$origin.send_message_id"
    }
    },
    "outs": {
    "success": 19,
    "error": 20
    }
    }
Last updated on Jan 29, 2023
Previous
SQL
Next
Scheduler
  • Description
  • Structure
  • Errors
  • Example
© 2015 - 2025 Altcraft, LLC. All rights reserved.