Syncing a CRM with a Process Manager = stage-based workflow automation!

Showcase Doc Show and Tell
1

I’ve been working independently on a CRM and a process/project/task manager, and finally brought the two of them together. Here’s a YouTube demo of the current state of doc.

The combination allows Hubspot-style workflow automation, where an opportunity (deal) moving through a pipeline can trigger an process (SOP) at any pipeline stage. You can build out processes with task assignments, dependencies, and estimated durations. When triggered, the process spawns a project and tasks with the appropriate assignments.

Thanks to the current state of cross-doc, the opportunity is updated in the CRM to show the new project. Pretty cool!

Looking forward to continuing to deepen support for continuous improvement of business processes. Ask me anything!

4 Likes
2

Nice work, it looks great!

For your automations, are you using the built-in Coda automation functions or are you having a formula push buttons in the background?

2 Likes
3

Thanks Mike - the main automations are Coda’s, so there’s the expected server-side delay.

1 Like
4

This is a bit on the sidelines, but how did you achieve those horizontal rules in the row detail layout? :smiley:

1 Like
5

I got so excited when I saw your post.

The project in currently working on is pretty much exactly what you’ve just described!

I’m in way over my head with it all. Cannot wait to watch your YouTube video about it.

*Edits for typos (I am genuinely excited by this, and rushed the message).

1 Like
6

Great timing then - glad you found the post!

I’m not sure how much help you’ll get from the video, but feel free to ask any specific questions here or reach out privately.

1 Like
7

Well I did say ask me anything!

I have a rectangle formula on a settings page, named “Modal Line Formula”. Then in any table I can add a text column and call the Modal Line Formula. In the modal I remove the label and centre it.

image
image1627×1039 110 KB

image
image2199×1130 172 KB

4 Likes
8

That’s clever! I have a bunch of views that desperately need some visual separation for the items and using this trick is going to help the users a lot.

1 Like
9

Yeah exactly what I use it for. The other thing I do sometimes is make section header columns in the same color as the modal line. Just a text column with whatever the header text is, in a _Color formula (like _Color(“blue”,“my header”). Then in the layout remove the label and make it H2, put it beneath a line to define the section.

1 Like
10

I started thinking this could be combined with drawing SVGs. So came up with this: :smiley:

2 Likes
11

If possible, can you please give a bit more detail about where in the process automations are being utilized?

2 Likes
12

For sure - the primary automation is in the process manager. When an opportunity status in the cross-doc CRM table is updated, the corresponding process is run (button push in the process row).

The rest of the “automations” follow off of that button push, where a project and tasks are created from the template process and its steps. It’s a long one, and getting the dependencies to transfer over was pretty difficult.

2 Likes
13

I’ve been working on something similar to what you’ve built, but I have a question about permissions and structure.

Initially, I had everything in a single doc, but now I’m realizing it might be better to split things up.

My main concern is permissions—how do you manage access across different parts of the system?

It’s great to have a company or contact from the CRM linked to a project or task in the task management system, but I wouldn’t want sensitive data like deals or opportunities to be accessible to everyone.

What approach have you taken to isolate certain information while still keeping everything somewhat connected and in sync?

1 Like