Callback blocks
Requires version 0.8.61 or greater.

Callback blocks are part of your pipeline but don’t run as individual steps in your pipeline like data loader blocks, transformer blocks, etc. However, callback blocks are associated to other blocks within the pipeline (e.g. data loaders, transformers, data exporters, etc).

After those other blocks are executed, any associated callback blocks will also be executed depending on the status of the parent block.


  1. Your pipeline has the following blocks:

    1. load_data_from_api (data loader)
    2. clean_column_names (transformer)
    3. save_data (data exporter)
  2. Then, you add the following callback block to your pipeline:

    def hello_world(parent_block_data, **kwargs):
        # some code...
    def alert_me(parent_block_data, **kwargs):
        # some code...
  3. You associate the above callback block to the following 2 blocks:

    • load_data_from_api (data loader)
    • clean_column_names (transformer)
  4. When you run the pipeline, it’ll execute the load_data_from_api (data loader) block first. It successfully completes. Then, the callback block will run and execute the function hello_world.

  5. Next, the pipeline will execute the clean_column_names (transformer) block. It fails due to some error. The callback block will run and execute the function alert_me.

How to add callbacks to your pipeline

  1. Create a new pipeline or open an existing pipeline.
  2. Edit the pipeline.
  3. On the right side of the page, click the Callbacks icon in the navigation. If you don’t see it, try expanding the right area of the page.
  4. Click the button + Callback block.
  5. In the callback block’s code, add a function and decorate it with @callback. You can have as many functions in a callback block as you want.
  6. Use @callback or @callback('success') to decorate a function that should only run when the parent block successfully completes.
  7. Use @callback('failure') to decorate a function that should only run when the parent block fails.

Supported callbacks


Execute callback function when block runs successfully.

def only_run_this_function_on_success(parent_block_data, **kwargs):


Execute callback function when block fails.

def only_run_this_function_on_failure(parent_block_data, **kwargs):

Positional arguments

The 1st positional argument is the data output of the callback block’s parent block.

Positional arguments are only supported in Mage versions >= 0.8.81.

Keyword arguments

Here are the keyword arguments that are available in each callback function:

NameDescriptionSample value
block_uuidCallback block UUID.'fireball_callback'
dsDate string when the parent block started executing.'2023-12-25'
eventA dictionary containing metadata from an event triggered pipeline.{}
execution_datePython datetime object for when the parent block started executing.datetime.datetime(2023, 4, 26, 20, 28, 17, 335254, tzinfo=datetime.timezone.utc)
execution_partitionPartition used for the parent block when it was executed.'207/20230426T202817'
hrHour string when the parent block started executing.'20'
pipeline_runPython pipeline run object associated to the current run.PipelineRun(id=2357, pipeline_uuid=fire_etl, execution_date=2023-04-26 20:28:17.335254+00:00)
pipeline_uuidUUID of the current pipeline.'fire_etl'
__inputFor version >= 0.8.81. See below for more details.{ 'some_block_uuid': {} }

__input keyword argument

For versions >= 0.8.81.

If your callback function is defined to only accept keyword arguments and no positional arguments, you can access the callback block’s parent block’s data output by accessing the key labeled __input in the callback function’s keyword arguments.

The value of the __input key is a dictionary. The keys in that dictionary are named after the callback block’s parent block’s UUID.

For example, if the callback block’s parent block’s UUID is load_api_data, then this is how you would access load_api_data’s data output:

def callback_for_load_api_data(**kwargs):
    data_from_parent_block = kwargs['__input']['load_api_data']

Data integration pipelines only

The following keyword arguments are only available in callback functions with parent blocks in a data integration pipelines:

NameDescriptionSample value
destination_tableThe table name that the source data is being exported to.'dim_users_v1'
indexThe order in which the parent block executed compared to other blocks of the same type.0
is_last_block_runBoolean value for whether or not the parent block was the last block ran for the block type in the pipeline.True or False
streamThe name of the source stream (or table) that the parent block is syncing for.'stripe_transactions'


For versions < 0.8.61.

Adding a callback to your block

  1. Create a block as normal.
  2. In the top right of the block, click the triple dot icon which should open up a menu with more options. Click “Add callback”.
  3. You should now see another code editor under the main editor for your block. Block callback
  4. You can add an on_success callback and/or a on_failure callback. These callbacks will run after your block run completes or fails. When you run your block in the pipeline edit page, it will also run the callback depending on the status of the block.
  5. The callback function will be passed your pipeline’s runtime variables as keyword arguments, so you can use the same kwargs.get('<variable>') syntax in your callback.