Documentation / Activation and Setup / Duzz Bot

Overview

Further Duzz documentation: User settings

The Duzz Bot is a way to communicate any updates you have made on project without having to make a manual update to the status feed. The bot will post an update to the feed for a project when you make any changes to any fields for a project. Maybe you updated the changed the Status for a project to ‘Completed.’ The bot will post that as an update. This indicates to your customers the timeline of when things were completed with a timestamp.

Status Feed Bot

Now in order for the bot to work when you update fields, you need Advanced Custom Fields set up first. You can find information about that here. Once that is set up you can follow the directions below to complete your bot setup

One thing the bot does without ACF is all updates not related to field updating. The bot will timestamp when a project was created, when an invite was sent, when a custom accepts an invite or when a customer creates a project themselves. Bottom line: you know when everything happens. It does this out of the box without having to set anything up.


Setting up the Duzz Bot

Once ACF is setup, follow these instructions:

  1. Go to your WordPress Dashboard, and then go to the Duzz Custom Portal settings at the top of your menu. This will go to the main Duzz settings menu.
  2. Duzz settings
  3. Then go to towards the bottom of the main menu. Look for the sections for ‘ACF Group’ and ‘Remove Keys.’ Both of these program the bot.
  4. First though, lets do the ‘ACF Group’ section. When you connect ACF with Duzz, Duzz automatically creates group 9900 (named ‘Duzz Custom Fields’) but if you create any more ACF groups, you will need to get the post ID for that group (not the group ID). ACF creates groups by creating posts. So if you click on the group, the group URL will look like this: https://duzz.io/wp-admin/post.php?post=9900&action=edit and you will notice group number 9900 in there.
  5. If you want to create another group so you can move separate some of the fields for organization, then you go to this page in ACF:
  6. Duzz Create Group
  7. Then click on ‘Add New’ to create a new group
  8. Then go back to the group page and go to ‘Duzz Custom Fields’ where you can choose any fields you want to move over. If you hover over any fields you will notice a link for ‘move’ where you can move the field to another group. You can add these group numbers to ‘ACF Group’ in the Duzz settings if you want the bot to notify when these fields are updated.
  9. The next thing you want to do is update the ‘Remove Keys’ section which controls which fields you do not want the bot to add updates for.You can see that some field keys are automatically added.
  10. ACF Key 1 has the key for the field last_updated which updates the time for the last time the project was updated. If this key was not removed for the bot, it would add an extra bot notification every time anything is updated which would be an annoying glitch.
  11. You will then see in ACF Key 2 is the key for customer_ip which is the customer IP address which you do not want displayed in the feed.
  12. If any of these fields change keys you will want to update these.
  13. In ACF Key 3 you can add any other field you want to remove from the bot.
  14. If you want to remove any more than 3 fields, then create a new group and move all those fields to that new group and don’t add that group to ‘Acf Group’ and the bot will not add updates for those fields.

  15. Status Feed system

    Github: Status feed

    The ‘Duzz Bot’ operates within the status feed. Any Bot updates added to the feed are added with the duzz_add_to_status_feed in the Duzz_Status_Feed PHP class of the plugin. It knows which metadata to include as an update based on the ACF group added to the ‘Acf Group’ in the Duzz settings mentioned above. This saves to the options name duzz_settings_email_settings_field_data which you can see controls the duzz_add_to_status_feed function.