# Wordpress

{% hint style="info" %}
The content of this documentation is under revision and may change. We appreciate your understanding as we work to improve it.
{% endhint %}

**Wordpress** manages posts and users using the Wordpress API.

## **Parameters**

Take a look at the configuration parameters for the connector. Parameters supported by [Double Braces expressions](https://docs.digibee.com/documentation/connectors-and-triggers/double-braces/overview) are marked with `(DB)`.

### **Required tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Dynamic Account</strong></td><td>When active, the connector will use the account dynamically. Otherwise, it will use the account statically.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Account Name</strong> <code>(DB)</code></td><td>The name of the dynamic account used by connector. This account must have been previously configured in a <a href="../tools/store-account"><strong>Store Account</strong></a> connector in the pipeline for this process to take effect. It is only available if the <strong>Dynamic Account</strong> parameter is active.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Account</strong></td><td>The account used by the connector. It is only available if the <strong>Dynamic Account</strong> parameter is inactive.</td><td>N/A</td><td>Account</td></tr><tr><td><strong>Operation</strong></td><td>The endpoint operation.</td><td>N/A</td><td>String</td></tr><tr><td><strong>URL</strong> <code>(DB)</code></td><td>The Wordpress API URL from your site, for example <a href="http://myblog.com/wp-json/">http://myblog.com/wp-json/</a></td><td>N/A</td><td>String</td></tr><tr><td><strong>Fail On Error</strong></td><td>If the option is activated, the pipeline's execution with an error will be interrupted. Otherwise, the pipeline execution proceeds, but the result will show a false value for the <code>"success"</code> property.</td><td>False</td><td>Boolean</td></tr></tbody></table>

### **Optional tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Operation Detail</strong></td><td>The second part of an endpoint operation, which is needed only when the endpoint semantic isn’t enough, for example wordpress:post:delete.</td><td>N/A</td><td>String</td></tr><tr><td><strong>API Version</strong> <code>(DB)</code></td><td>The Wordpress REST API version.</td><td>2</td><td>String</td></tr><tr><td><strong>Criteria</strong> <code>(DB)</code></td><td>The criteria to be used with complex searches.</td><td>N/A</td><td>JSON</td></tr><tr><td><strong>Force</strong></td><td>When active, it forces the definitive deletion and bypasses the trash.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>ID</strong></td><td>The entity ID. It should be configured when the operation performed requires a specific entity, for example. when deleting a post.</td><td>N/A</td><td>Integer</td></tr><tr><td><strong>User</strong> <code>(DB)</code></td><td>The authorized user to perform data manipulation operations.</td><td>N/A</td><td>String</td></tr></tbody></table>

### **Documentation tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Documentation</strong></td><td>Section for documenting any necessary information about the connector configuration and business rules.</td><td>N/A</td><td>String</td></tr></tbody></table>

{% hint style="info" %}
If the execution is successful, the output of the execution should have at least a property `"success": true.`
{% endhint %}