---
title: "remotepublish-page macro"
canonical: "https://support.appfire.com/space/CDML/649628625/remotepublish-page%20macro"
format: markdown
---
> Macro (aura-html)


## Overview

> Macro (excerpt)
> 
> Publish a page to a remote Confluence instance

The `remotepublish-page` macro is used as an [action](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649858941) to publish content to a space on a different Confluence Server, Data Center, or Cloud instance.

- content is developed in a space on the source server
- published content is pushed to a space on a remote server

For more information, see: [Remote-space publishing](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649728423)

## Requirements

> 📝 This macro requires the installation of the [Comala Remote Publishing app for Comala Document Management](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649660565).

Before using this macro, you must ensure **both the source and target Confluence instances** are properly configured.

For more information, see [Remote-space publishing](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649728423).

## Where to use it?

Optional.

One or more `remotepublish-page` macros can be put in a [trigger macro](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649859133).

## Parameters

| Parameter | Required | Default | Notes |
| --- | --- | --- | --- |
| `config_name` | :check_mark: |  | The name of the remote publishing configuration profile to use.<br>- `remotepublish-page=`<*config_name*><br>where *config_name* is the name of the remote publishing profile added in the remote space configuration in the Document Management dashboard.<br>> ℹ️ The configuration profile defines the remote server URL and destination space, as well as the username and password for an account on that server which has Edit Content permissions in the target space. |

## Basic example

This example remote-publishes to a server defined by the "`MyDestination`" remote publishing configuration.

```plaintext
{workflow:Remote-space publishing}
   {state:Editing|submit=Review}
   {state}
   {state:Review|approved=Published|rejected=Editing}
      {approval:Review}
   {state}
   {state:Published|updated=Editing|final=true}
   {state}
   {trigger:statechanged|state=Published}
      {remotepublish-page:MyDestination}
   {trigger}
{workflow}
```

> 📝 The `final=true` parameter on the `Published` state is not required for remote-space publishing, however it helps to clarify which versions of content are published in the source space.

## All examples

> Macro (contentbylabel)

## See also

External links

- [Remote Publishing for Comala Document Management app](https://marketplace.atlassian.com/plugins/com.comalatech.remotepublishing/server/overview)

[Workflow Authoring Guide](https://appfire.atlassian.net/wiki/spaces/CDML/pages/648611901)

- [remoteremove-page](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649628704)
- [Remote-space publishing](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649728423)

| [‹ Back to Remote-space Publishing](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649728423) |
| --- |